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

The description discloses behavioral traits beyond annotations: it is a write operation (consistent with destructiveHint=true), requires signer mode and policy approval, is a paid action with cost preview, and has routing restrictions. No contradiction with annotations.

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?

The description is relatively concise at a few sentences, with the key action stated first. However, some boilerplate like 'Intent: SAP MCP tool workflow' could be tighter, and the structure could be more streamlined.

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?

Given high schema coverage and existing annotations, the description covers purpose, usage context, prerequisites, pricing, and routing. It could mention what happens post-cancellation, but the output schema likely covers return values. Overall sufficiently complete.

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?

The input schema has 100% coverage with descriptions for both parameters. The tool description does not add additional meaning beyond what the schema already provides, so baseline score of 3 is appropriate.

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 description immediately states 'Cancel a recurring subscription,' which is a specific verb and resource. This clearly distinguishes it from sibling tools like sap_create_subscription or sap_fund_subscription.

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 provides context about when to use this tool (e.g., 'Estimate or fetch state before creating escrows or settling calls') and mentions prerequisites (signer mode, policy approval). It also advises against calling it as a paid hosted write and suggests alternatives like sap_payments bridge when user signing is required, but could be more explicit about when not to use it.

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