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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive behavior. The description adds a 'Free read' claim, but the same description later says 'Pricing: paid read-premium; estimate first', creating an internal contradiction about cost expectations. The signer-boundary note is useful, but the conflicting pricing language undermines transparency.

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 concise, but the appended SAP MCP execution guidance is generic boilerplate that repeats the same 'estimate first, then use sap_payments_call_paid_tool' instruction under both Pricing and Routing. Several sentences do not earn their place for this specific tool.

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 single-parameter read with full schema coverage, an output schema, and strong annotations, the core calling information is present. Completeness is weakened by the contradictory 'Free read' versus 'paid read-premium' language and by the lack of any clarification distinguishing this tool from the similarly named Phoenix read tools.

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 the single 'authority' parameter as a base58 trader wallet public key and marks it REQUIRED, with 100% schema description coverage. The description repeats the format and requiredness but adds no new semantic details, so it remains at the schema-covered baseline.

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 ('Get') and resource ('Phoenix trader PnL history'), and it identifies the required wallet address. It does not explicitly name or differentiate nearby sibling tools like sap_phoenix_get_trader or sap_phoenix_get_trader_state, but 'PnL history' is specific enough to convey the core purpose.

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 an explicit precondition: the trader's wallet address must be provided in base58. However, it provides no when-to-use versus alternatives or when-not-to-use guidance, and the SAP MCP execution guidance is generic pricing/routing boilerplate rather than tool-selection guidance.

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