get_market_details

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds the useful trait that the orderbook snapshot is 'live', but does not mention permissions, error conditions, or data freshness beyond that. Minimal but not misleading.

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?

The description is a single, front-loaded sentence that directly states the tool's purpose and a key feature. There is no wasted language or irrelevant detail.

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?

The tool has a simple interface with one required parameter and an output schema, so the description doesn't need to list return fields. However, the lack of parameter semantics and explicit usage comparisons to sibling tools leaves some gaps in contextual completeness.

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% and the description does not explain the 'condition_id' parameter. The agent must rely on the parameter name alone, which may be insufficient for a new user. No additional meaning is provided beyond the schema fields.

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 clearly states the tool retrieves full details for a specific market, including a live orderbook snapshot. It uses a specific verb and resource, but it doesn't explicitly differentiate from sibling tool 'get_orderbook', which also deals with orderbooks.

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?

The phrase 'for a specific market' implies it is intended for lookups by market identifier, not for searching or listing. However, no explicit guidance is given about when to use this tool over get_orderbook or other alternatives, and no exclusions are stated.

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