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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds useful context: 'Free read — stats come from one batched /v1/markets/stats/latest call' discloses efficiency and the exact endpoint. But 'Free read' directly conflicts with the adjacent SAP guidance saying 'Pricing: paid read-premium; estimate first,' leaving the agent with contradictory cost signals that could misroute its 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 tool-specific portion is tight and front-loaded: three sentences covering scope, fields, use case, and data source. However, the long SAP execution guidance block is duplicated verbatim in the input schema description, adding bulk, and its 'paid read-premium' phrasing undercuts the 'Free read' lead.

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 zero-parameter read tool with an output schema and safety annotations, the description covers purpose, content, use case, data source, and platform routing guidance — nothing critical is missing. The remaining gaps are the unresolved free-vs-paid pricing contradiction and no differentiation from closely related market-data siblings.

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 is 4 — there is nothing the description must document. The description goes further by listing the output fields the agent can expect, which compensates well for the empty input 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 description opens with a specific verb and scope — 'List all Phoenix perp markets WITH live stats merged' — and enumerates the exact output fields (symbol, mark price, oracle price, 24h volume, open interest, funding rates, leverage tiers). The emphatic 'ALL' and the plural 'markets' clearly distinguish it from the singular sibling sap_phoenix_get_market, so an agent can tell them apart without opening schemas.

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?

'Sorted data source for opportunity ranking and dashboards' provides a clear intended use case, which is enough to signal when this tool is appropriate. However, it names no alternatives or exclusions — it never says when to prefer sap_phoenix_get_market_stats or sap_perp_markets instead.

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