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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description adds nothing beyond that: it doesn't say whether results are cached, unpaginated, sorted, or scoped to the caller's account.

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?

Two short fragments, front-loaded with the purpose; nothing is padded. The trailing endpoint path is mildly redundant with the tool name, but it is a legitimate disambiguator rather than 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?

For a trivial no-parameter list endpoint with full annotation coverage and no output schema, the description is minimally sufficient to call the tool. It is incomplete on the one thing that matters for a 'get all' call — result size/pagination behavior — but nothing an agent needs to invoke it correctly is strictly absent.

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 takes zero parameters, so the schema has nothing to explain and the description cannot add parameter meaning. Baseline 4 applies for a no-argument tool.

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 all Prediction exchanges') and even gives the underlying endpoint, so the agent knows this is a read of the prediction-market exchange catalog. It does not explicitly contrast itself with near-name siblings like get_exchange, get_exchange_cex or get_exchange_dex_chain, so the differentiation is left to the word 'Prediction'.

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?

No statement of when to choose this over get_exchange, get_exchange_cex, get_exchange_dex_chain, get_exchange_with_exchange_rate or get_api_prediction. The scope is implied only by the adjective 'Prediction'; there are no prerequisites, exclusions, or alternative-routing hints.

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