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

The annotations already declare readOnly/openWorld/idempotent, but the description goes far beyond them by disclosing graceful degradation, the figi_candidates ambiguity behavior, the explicit unresolved list, internal cascading lookups, and ownership data when LEI resolves. No statement contradicts the 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?

The description is one massive wall of text with long parenthetical asides and repetitive query-phrasing examples. It is front-loaded enough to state purpose early, but the content would be far more readable as bullets or short sections. It is functional but not concise.

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 tool with no output schema, the description thoroughly covers return values and edge cases: identifiers with source labels, unresolved, figi_candidates, RxCUI plus ingredient/brand and citation, and fallback behavior. It also covers ownership children, non-US issuers, and exact input expectations, so nothing needed to call it correctly is missing.

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%, yet the description adds substantial meaning: accepted input forms (ticker, CIK, ISIN, name), the ISIN-to-LEI mapping flow, and the warning to pass the entity name only rather than the full noun phrase. These details turn the generic 'value' parameter into a precisely understood input.

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 states a specific action—'resolve a user-spoken NAME to the canonical/official identifiers other tools require as input'—and reinforces it with concrete examples like ticker, CIK, LEI, and RxCUI. It clearly distinguishes itself from profile or research tools by emphasizing that its output is identifiers needed by other tools. The core purpose is unmistakable even though the description is long.

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?

It contains the explicit directive 'Use FIRST whenever you have a name but need an ID,' which gives clear when-to-use guidance. The supported types and the bond/issuer warning add valuable usage context. However, it never names an alternative tool or states when not to use it, so it falls just short of a 5.

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