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

Annotations already cover read-only, idempotent, non-destructive behavior. The description adds some context about the signer boundary, but it then undermines itself by calling the tool 'Free read' while also stating 'Pricing: paid read-premium.' This internal contradiction obscures the actual behavioral and cost characteristics.

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 line is appropriately concise and informative, but the rest is generic SAP boilerplate that repeats the same intent, pricing, routing, and signer-boundary content also present in the input schema. The duplicated guidance adds noise and contradicts the earlier 'Free read' statement.

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?

Despite a simple one-parameter schema and existing output schema, the description leaves a critical ambiguity unresolved: is this a free read or a paid premium read? The routing guidance assumes a paid flow, while the first sentence says 'Free read.' An agent cannot confidently decide whether cost estimation is required before invocation.

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?

There is only one parameter, symbol, and the schema already documents it with 100% coverage including examples. The description essentially repeats the schema content and adds no additional semantic detail, so it meets the baseline but does not go beyond it.

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 clearly states the action and resource: 'Get Phoenix market metadata for a symbol (e.g. SOL, BTC).' This is specific enough for an agent to know what the tool returns, though it does not explicitly distinguish itself from sibling read tools like sap_phoenix_get_market_stats or sap_phoenix_get_markets.

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 provides no explicit guidance on when to choose this tool over similar Phoenix market tools. The generic SAP execution guidance talks about pricing and routing, but it does not help an agent decide between get_market, get_markets, get_market_stats, or get_market_fills.

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