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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds value beyond these: it explains the x402 payment mechanism, the hosted nature requiring cost estimation, and the signer boundary rule. No contradictions 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 front-loaded with the core purpose in two sentences, followed by structured guidance. The guidance section is somewhat lengthy but each part is necessary for correct usage. Could be trimmed slightly, but overall efficient.

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?

The tool has no parameters and an output schema exists, so the description need not cover return values. It still mentions the returned fields (price, custody address). The guidance covers all contextual aspects: payment, routing, and security. Fully adequate for the tool's simplicity.

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 zero parameters, so schema coverage is 100%. The description does not need to add parameter semantics, but the baseline for 0 parameters is 4. The description appropriately avoids discussing nonexistent parameters.

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 clearly states the tool fetches 'latest oracle trading prices for all Adrena assets' and specifies it returns 'price and custody address for each traded asset'. This is a specific verb-resource pair, distinguishing it from other read tools like sap_adrena_get_prices and sap_adrena_get_markets.

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 includes explicit SAP MCP execution guidance covering intent (read/discovery), pricing (priced by x402), routing (call sap_estimate_tool_cost first, use sap_payments_call_paid_tool if needed), and signer boundary (no keypair bytes). This provides clear when-to-use instructions and excludes inappropriate usage.

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