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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds useful signer-boundary context, but the cost guidance is internally contradictory: it says 'Free read' yet later labels 'Pricing: paid read-premium.' This contradiction undermines an agent's ability to predict the actual cost/behavior of the call.

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 first sentence is front-loaded and clear, but most of the description is generic SAP MCP execution guidance repeated nearly verbatim in the input schema. For a zero-parameter read tool, this is excessive boilerplate that distracts from the tool's actual purpose.

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 is simple, has an output schema, and the annotations cover the read-only/idempotent safety profile. The description states what the snapshot includes and notes the signer boundary, but the contradictory 'Free read' versus 'paid read-premium' messaging leaves an agent uncertain about prerequisites and cost.

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 tool has zero parameters, so the baseline score of 4 applies. There is no parameter semantics burden for the description to carry, and the schema description is fully comprehensive at 100% coverage.

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 states a specific verb and resource: 'Get Phoenix exchange snapshot: all markets, status, configuration.' This clearly identifies an exchange-level read rather than a single-market or orderbook query, though it does not explicitly name sibling alternatives like sap_phoenix_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?

No guidance is given for when to choose this tool over related siblings such as sap_phoenix_get_markets or sap_phoenix_get_market. The 'SAP MCP execution guidance' is about payment routing and cost estimation, not tool selection, so it does not help an agent decide between alternatives.

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