get_instrument_details

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

Discloses that isInternalInstrument indicates restricted trading, and includes rate limit (120 requests/60s). These details go beyond the readOnlyHint annotation, adding valuable behavioral context.

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?

Concise and well-structured, front-loaded with purpose and key output details. The sample return and rate limit are useful, though the description could be slightly more streamlined.

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 single-parameter tool with full schema coverage and an output schema, the description is complete: it explains the return structure, a key boolean field, rate limits, and prerequisite step (resolve ID).

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 coverage is 100% and the description's example ([1001]) adds minimal value beyond the schema description. No additional semantics about parameter behavior (e.g., maximum IDs) are provided.

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 display data for instruments by ID, listing specific fields like name, symbol, type, exchange. It distinguishes itself from sibling 'search_instruments' by implying this tool is for known IDs.

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 instructs to use 'search_instruments' to resolve a ticker to an instrumentId first, providing clear when-to-use and alternative. Also mentions rate limit context.

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