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

With no annotations present, the description carries the full burden and does disclose a critical operational fact: it costs $0.02 via x402/USDC, meaning the caller must be prepared for a paid request. It also scopes the narrative ('how the odds moved, not why'), which prevents the agent from expecting causal analysis. It does not cover failure modes for invalid ids or latency.

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?

A single dense sentence that front-loads the deliverable and ends with the cost, so the most decision-relevant facts come first. It is packed but every clause maps to a distinct output element or constraint; no filler.

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?

There is no output schema, yet the description enumerates the return contents closely enough that an agent knows what it will get back. Combined with the disclosed price and payment rail, this is nearly complete for a one-parameter tool; only error behavior and how to source a valid market id are missing.

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?

Schema coverage is 0%, so the description must compensate; it partially does by making clear the single parameter selects exactly one market ('one Vatic market'), ruling out batch or multi-market use. It adds nothing about the UUID format, where to obtain a valid id, or what happens with an unknown id, so the compensation is only partial.

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 and resource ('AI summary of one Vatic market') and enumerates exactly what the summary contains: crowd positioning, 24h and 7-day change, biggest moves, and a short written narrative. That distinguishes it in substance from the raw-data siblings like get_market or market_history, though it never names an alternative explicitly.

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?

Usage is only implied: the phrase 'AI summary' plus the $0.02 price tag signals that this is the interpretive, paid option versus raw market data. There is no explicit 'use this when…' or 'use get_market instead when you only need raw numbers,' so the agent must infer the tradeoff itself.

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