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

Annotations already carry readOnlyHint, idempotentHint, and destructiveHint. The description adds value by mentioning the paid read-premium model, estimate-first requirement, and signer boundary. But the phrase 'Free read' directly conflicts with 'paid read-premium' in the same description, creating ambiguity about cost behavior despite the annotations being consistent.

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 appropriately front-loaded, but the rest of the description is a large block of generic SAP MCP execution guidance that is repeated verbatim in the input schema. It is boilerplate rather than tool-specific information, making the description longer than necessary without earning its place.

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 one-parameter read tool with an output schema and strong annotations, the description covers the main operational concerns: cost, routing, and signer boundary. The main gap is the unresolved 'free read' vs. 'paid read-premium' ambiguity, but the output schema and annotations fill most of the remaining context an agent needs.

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 only parameter, 'symbol', is documented as 'Market symbol' in the schema. The description adds no additional meaning, format, or examples for the parameter. Baseline 3 is appropriate because the schema fully handles parameter documentation.

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 and resource: 'Get Phoenix funding rate history for a symbol.' The 'Phoenix' qualifier separates it from similar read tools like sap_perp_funding_history and the many other sap_phoenix_* read tools. The first line alone is enough for an agent to recognize the operation.

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?

Provides useful context for how to invoke the tool: read/discovery workflow, estimate cost first, and route through sap_payments_call_paid_tool when x402 cannot be replayed. However, it never explains when to prefer this tool over sibling Phoenix or perp funding-history tools, and it gives no exclusion criteria. Usage is implied rather than explicitly scoped against alternatives.

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