resolve_instrument

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

No annotations provided, but description fully compensates: discloses conservative matching ('matched=false' rather than guessing), states it does not price instruments or resolve crypto, and mentions return includes 'provenance and a signed receipt'. Very transparent.

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?

Highly structured with clear sections (PURPOSE, GUIDELINES, PARAMETERS, LIMITATIONS, EXAMPLE). Each sentence adds value, no fluff. Efficient and well-organized.

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?

Comprehensive for a resolution tool with no output schema: describes what is returned (FIGI records, provenance, receipt) and limitations (no pricing, no crypto). Covers all essential aspects for correct invocation.

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 has 67% coverage; description adds meaningful context for all 3 parameters: explains `query` purpose, notes `idType` auto-detection, and specifies range and default for `maxResults`. Goes beyond schema info.

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 the verb 'resolve' and resource 'security identifier to canonical FIGI records via OpenFIGI'. Distinguishes from sibling tools by focusing on instrument resolution and disambiguation.

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 advises to call 'BEFORE acting on any claim, order, or document', explains why (disambiguation, provenance), and suggests preferring explicit identifiers. Provides clear context for when and how to use.

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