list_markets

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

No annotations provided, so description carries full burden. It mentions 'current' markets but lacks disclosure on caching, rate limits, authentication requirements, or what happens when no markets match the filter. With output schema present, it correctly omits return structure details, but other behavioral traits are missing.

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?

Front-loaded with a clear purpose statement followed by a structured Args section. No redundant or wasted sentences, though the docstring-style formatting is slightly verbose compared to inline prose.

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?

Adequate for a simple listing tool with 2 parameters and an output schema (which handles return documentation). However, gaps in behavioral transparency and sibling differentiation leave it incomplete given the rich ecosystem of 20+ related tools.

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%, but the Args section excellently compensates by documenting both parameters: it specifies valid string values for 'source' ('kalshi', 'polymarket', or empty for all) and the valid range for 'limit' (1-100), adding crucial semantic meaning absent from the raw schema.

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 specific verb (List) + resource (prediction markets) + scope (Kalshi and Polymarket platforms). However, it does not differentiate from siblings like 'search_markets' or 'screen_markets' which likely overlap in functionality.

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?

Provides no guidance on when to use this tool versus alternatives such as 'search_markets', 'get_market', or 'screen_markets'. No prerequisites or exclusions are mentioned.

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