Invoke Write SAP Capability

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=false, idempotentHint=false, openWorldHint=true and destructiveHint=false, so the safety profile is largely covered structurally. The description adds one genuinely useful behavioral fact — that the underlying tool's validation and result semantics are preserved through the wrapper — but says nothing about auth requirements, failure modes, or the non-idempotent retry hazard.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the action and immediately followed by the sequencing constraint. No filler, though the second sentence about preserved validation reads as a vague reassurance rather than concrete information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a generic invocation proxy with a nested free-form arguments object, an unexplained hash parameter, no output schema — and the description omits the parameter contract entirely. Given that an agent must construct arguments blindly and source the hash externally, the definition is under-specified for the tool's complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for all three parameters, so the description must carry the burden and does not. It never explains that name identifies the capability, that arguments is the free-form payload forwarded to it, or that the 64-hex schemaHash must be obtained from sap.capability.describe — the most opaque and error-prone field in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The verb 'invoke' plus the qualifier 'write capability' tells the agent this is a mutating proxy call, and the name pairs it against the sibling verbs invoke_read and invoke_destructive. However, 'write capability' is a generic abstraction that never says what class of operations it covers or how it differs from the destructive sibling, so differentiation rests almost entirely on the tool name itself.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description imposes a clear prerequisite sequence — call it 'after sap.capability.describe' — which is real, actionable routing guidance. It stops short of saying when to prefer this over sap.capability.invoke_destructive or how to decide a capability is a 'write' rather than a 'read', so usage is implied rather than explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.