Get Quote

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

The description and annotations align: readOnlyHint and idempotentHint are consistent with the term 'snapshot'. However, the description adds little beyond the annotations about side effects or failure modes.

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, focused sentence with no redundant wording. It front-loads the action and object clearly.

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?

Given the presence of an output schema and read-only/idempotent annotations, the one-sentence description is largely sufficient for typical usage. It could be slightly more explicit about what 'fully specified' entails, but it is not incomplete in a harmful way.

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?

The top-level 'instrument' parameter lacks a direct description, though the nested SymbolSpec definition provides some field-level detail. The phrase 'fully specified instrument' hints at required completeness but does not fully explain which fields are essential for a quote.

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 action ('Get') and the resource ('market-data snapshot') for a fully specified instrument. It is not overly broad, though it does not explicitly distinguish itself from siblings like get_option_snapshot.

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 'fully specified instrument' loosely implies a precondition but gives no explicit direction on when to use this tool versus alternatives such as get_option_snapshot or resolve_contract. No when-not guidance is provided.

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