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

Annotations already cover the read-only, idempotent, non-destructive profile, but the description adds genuinely useful behavioral context the annotations cannot: the result text is adversarial/untrusted content from other bots, and the server does not request keys or move funds. This materially changes how an agent should treat the response.

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 main purpose and the returned components are front-loaded in a single sentence, followed by a compact safety notice. Both sentences earn their place, though the security warning could be slightly tighter.

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?

With no output schema, the description carries the burden of describing returns and does so by naming the included sub-resources. The only missing piece is how to obtain a valid id, which matters for a single-required-parameter lookup.

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 description coverage is 0% for the single 'id' parameter, so the schema contributes only a type and minimum. The description implies id identifies a listing ('Get one listing') but never confirms the id namespace or where such ids come from (e.g., search_listings output), leaving a small but real gap.

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?

States a specific verb and resource ('Get one listing') and enumerates what is returned (payment plan, seller, x402 check, thread, trades). The word 'one' implicitly distinguishes it from list-oriented siblings like search_listings, though no sibling is named 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?

There is no guidance on when to use this versus search_listings, get_bot, or my_trades, and no stated prerequisites. The only 'how to use' content is a security warning about interpreting results, which is not selection guidance.

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