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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds value beyond that by stating 'Free read,' clarifying it is a free hosted call (no x402 required), and noting that hosted reads never receive keypair bytes while value-moving results must be finalized locally. These are useful behavioral disclosures about cost and signing boundaries that are not in the annotations. No contradiction found.

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 tool-specific portion is efficient: two sentences covering purpose and symbol formats. However, the SAP MCP execution guidance block is generic boilerplate (intent/pricing/routing/signer boundary) that likely repeats across every sap_* tool and adds little tool-specific signal. It dilutes the conciseness of an otherwise tight definition.

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?

For a simple one-parameter read tool with an output schema and annotations covering safety (readOnly, idempotent, non-destructive), the description covers the essential facts: what it returns (open interest), which symbol format is required, and execution routing (free direct call). The signer-boundary note addresses the main operational risk for this class of tool. Nothing critical is missing for correct invocation.

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 coverage is 100% (the 'symbol' parameter is documented with example SOL_USDC_PERP). The description adds genuine value by explaining the naming conventions: spot SOL_USDC vs perp SOL_USDC_PERP, and stock formats like MU.US_USDC and RFQ AAPL.US_USDC_RFQ. This clarifies which symbol forms are valid for this tool, going beyond what the schema provides.

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?

States a specific verb ('Get') plus resource ('Backpack open interest for a perp symbol') with a concrete example symbol (SOL_USDC_PERP). This is clear and tool-specific. However, it doesn't explicitly differentiate from sibling read tools like sap_backpack_get_ticker, sap_backpack_get_funding_rates, or sap_backpack_get_mark_price — the open-interest scope is implied by the name more than by contrast with alternatives.

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 SAP MCP guidance block states intent (read/discovery workflow) and that it is free to call directly, which gives some usage context. It does not name any alternative tool or state when NOT to use this one. The symbol-format examples (spot vs perp vs stock RFQ) implicitly tell the user which symbol forms apply here, but there is no explicit routing to a sibling for other data types.

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