get_market

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

Despite readOnlyHint annotation, description provides extensive behavioral context: lists return type (dict), notable fields including order-book edges, momentum, liquidity, and status flags. No contradiction with annotations.

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?

Compact and well-structured: purpose first, then usage guidelines, parameter explanation, and return field list. Every sentence adds value with no redundancy.

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?

Complete for a single-market retrieval tool: explains how to call it, what it returns (including key fields and their meanings), and how the output is structured. Output schema exists but description adds necessary context.

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?

Only parameter market_id is fully described: type (numeric string), example ('573655'), and origin (from search_markets, get_event, get_active_markets). Schema has 0% description coverage, so description entirely compensates.

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?

Clearly states 'Get full details for one market' with specific verb and resource. Differentiates from sibling get_event by specifying 'single specific question' versus 'whole topic'.

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?

Explicitly says when to use ('single specific question') and when not to ('For the whole topic, use get_event'), and tells how to obtain market_id from sibling tools.

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