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

Annotations already establish readOnlyHint=true and destructiveHint=false. The description adds that it is a snapshot and that hosted reads never receive keypair bytes, but it also contains a direct conflict between 'Free read' and 'Pricing: paid read-premium', which undercuts transparency about cost and payment flow.

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 sentence is clear and front-loaded, but the description then appends a long block of generic SAP MCP execution guidance that is also duplicated inside the input schema. The contradictory 'Free read' vs paid pricing adds noise rather than value.

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 output schema and annotations cover return structure and read-only behavior, and the required wallet address is stated. However, the conflicting free/paid statements leave an agent uncertain whether it must call an estimation and payment tool before invoking this read, which is essential context for this SAP tool family.

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?

Input schema description coverage is 100%, so the schema already documents 'authority' and 'traderPdaIndex'. The description repeats that the wallet address is a base58 public key but adds no new parameter semantics, matching the baseline for fully covered schemas.

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 a specific action and object: 'Get Phoenix trader state snapshot' and enumerates the contents (subaccounts, positions, collateral). It does not explicitly distinguish itself from sibling tools like sap_phoenix_get_trader or sap_phoenix_get_trader_pnl, so it misses the top score for sibling differentiation.

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?

There is no guidance on when to choose this tool over alternatives such as sap_phoenix_get_trader or sap_phoenix_get_trader_pnl. The only use-related statements are that a wallet address is required and that it is a 'Free read', and the free-vs-paid guidance is internally contradictory.

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