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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context that would otherwise be missing (no output schema exists): the returned fields and the fact that prices are probabilities in 0..1. It omits the important behavior that results default to open markets only.

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 sentences with no filler, and the price-unit clarification is placed immediately after the field list. The main flaw is that it is a sentence fragment rather than a front-loaded statement of the operation.

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 field enumeration does useful work on the return side. But for a two-parameter filtered listing tool, the absence of any filter semantics (especially the default status=open) leaves an agent unable to predict what it will get back or how to narrow results.

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%, so the description carries the full burden, yet it says nothing about the status enum (open/resolved/all, default open) or the category enum (crypto/general). The only parameter-adjacent hint is 'status' appearing in the return-field list, which is not tied to the input filter.

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 enumerates the fields of a market record (question, close time, bid/ask, last price, volume, status), which implies a listing operation but never states a verb or scope such as 'list all markets'. It does not distinguish itself from the sibling get_market, so an agent cannot tell from the description which one returns a collection versus a single market.

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 tool versus get_market, nor on when the status/category filters should be applied. The only implied usage is that it returns multiple markets, which the agent must infer from the field list.

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