list_markets

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

Description does not disclose behavioral traits beyond listing and filtering. With no annotations, the description carries full burden; missing details on pagination, response format, read-only nature, or authorization requirements.

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?

Description is one sentence plus a compact list of status codes. Every character serves a purpose; no wasted words. Front-loaded with the main action.

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 simple list tool with one optional parameter, the description covers the core functionality. However, missing details like default behavior (no filter returns all?), pagination, or response structure. Since no output schema exists, more context would be beneficial.

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?

Input schema describes 'status' as 'Filter by status code'. Description adds the exact mapping of codes (0=CREATED, 1=ACTIVE, etc.), providing meaningful context beyond the schema. This helps the agent choose correct values.

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?

Description clearly states 'List prediction markets' with a verb and resource. It distinguishes from siblings like 'get_market' which retrieves a single market, and other tools like 'get_market_trades' or 'get_price_history'.

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?

Description implies usage for listing markets with optional status filter, but does not explicitly state when to use this tool versus alternatives (e.g., for a single market, use get_market). No exclusions or when-not guidance provided.

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