[refactor] Use full words for abbreviated tool-interface field names (`op`, `args_into`)

[mmabrouk]

Context

While reviewing #4893, @mmabrouk flagged abbreviated / unclear names in the platform-op + direct-call
tool interfaces:

• "let's not use abbreviations whenever is possible unless widely used"
  (on op)
• "the variable naming here is not good, the names should be clear"
  (on the catalog fields)

The one contained, SDK-internal field (bind -> context_bindings) is handled in #4906. The
remaining names cross the public-edge config and the SDK<->runner wire, so they should be
renamed as one deliberate pass (apply the design-interfaces skill), not in a minor follow-up.

Names to address

op -> consider operation

The platform-op key. It appears on the public agent-config arm
({ "type": "platform", "op": "find_capabilities" }), the catalog (PlatformOp, PLATFORM_OPS,
get_platform_op, the op_catalog.py module name), the reserved id tools.agenta.<op>, the
interface inventory, and ~6 test files.

Decide first whether op clears the "unless widely used" bar. If it stays, close this part; if
not, rename to operation across SDK + config schema + inventory + tests.

args_into -> consider args_path / args_target

Where the model's args land in the request body. This is a wire field on ToolCall, so it
spans Python (tools/models.py, wire_models.py), the TS runner (services/agent/src/protocol.ts,
tools/direct.ts), the golden wire contract, and the cross-service docs.

Ask

Decide on the target names, then rename in one pass across SDK + TS + the golden contract + the
interface inventory + docs.

Convention (added to agent memory)

Prefer full words over abbreviations in new code unless the abbreviation is widely used.

[linear-code]

AGE-3842