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

Annotations already establish read-only, open-world, idempotent, non-destructive behavior. The description adds a 'Free read' claim and a signer-boundary note, but then contradicts 'Free read' with 'Pricing: paid read-premium' and paid-call routing guidance. This internal inconsistency undermines the extra behavioral context.

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 opening is tight and front-loaded, but the large 'SAP MCP execution guidance' block is generic, duplicated in the input schema, and contains a pricing statement that contradicts 'Free read.' It does not earn its place in the description.

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 operation with an output schema, the description covers the required input and the returned categories. However, the free-vs-paid ambiguity and the lack of distinction from similarly named sibling tools leave the context incomplete.

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 already documents 'authority' as a required base58 public key at 100% coverage, so the baseline is 3. The description adds practical meaning by explaining it is the trader's wallet address and by telling the agent to use its own address for self-queries, which goes beyond the schema.

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 first sentence names a specific operation ('Get Phoenix trader state') and enumerates the returned content (positions, orders, collateral). However, a sibling tool named sap_phoenix_get_trader_state exists, and the description does not differentiate this tool from it or from sap_phoenix_get_trader_pnl.

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 gives argument-level guidance: the authority must be provided, and the agent should use its own wallet address when querying its own positions. But it never says when to choose this tool over sap_phoenix_get_trader_state or sap_phoenix_get_trader_pnl, and provides no exclusions or alternative routing.

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