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

Beyond the annotations, the description discloses the upstream data sources, the GLEIF name-matching behavior, the inclusion of confidence and alternatives, and a per-call price with x402/Solana payment mechanics. It also provides an HTTPS fallback endpoint, which is meaningful operational context not present in 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 core purpose is front-loaded and the extra details about pricing and HTTPS are useful rather than filler. The first sentence is long and densely packed, but the overall definition remains efficient and structured.

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?

There is no output schema, so the description carries the burden of explaining return values; it does so by listing CIK, registrant name, exchange, sibling share classes, LEI, confidence, registration status, jurisdiction, and alternatives. Combined with input-format and payment details, this is sufficiently complete for an agent to call the tool correctly.

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 100%, so the schema already explains ticker, CIK, and the LEI boolean. The description adds the useful detail that BRK-B is accepted alongside BRK.B, but it does not explain the LEI toggle behavior or add much parameter-level guidance beyond the schema.

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 verb and resource: resolve a stock ticker or CIK to SEC CIK, registrant name, exchange, share classes, and LEI. It clearly distinguishes the tool's identifier-resolution role from filing search or financial-data siblings in substance, but it does not explicitly name or contrast those siblings.

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?

Usage is implied by the purpose and by the accepted input alternatives (ticker, CIK, BRK.B / BRK-B), but the description does not explicitly say when to use this instead of siblings such as sec_edgar_search, company_profile, or sec_financials. It also does not state when not to use the tool.

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