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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, and the description adds genuinely new traits: reporting exceptions surface as warnings, absence is not proof of no relationship, and each call costs $0.0057 USDC via x402 on Base mainnet. Disclosing the paid-invocation mechanism and the epistemic caveat is exactly the value-add expected beyond structured fields.

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?

Three sentences ordered purpose → caveat → cost, each carrying distinct information with no repetition of schema or annotation content. Slightly dense but front-loaded and free of filler.

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?

With an output schema present, return-shape explanation is unnecessary, and the description covers safety, cost, and failure semantics. The only remaining gap is practical detail on how the x402 payment is settled, which an agent would need before invoking a paid endpoint.

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 0%, so the single 'lei' parameter is documented only by its pattern; the description compensates partially by stressing 'exact LEI', which rules out fuzzy or name-based matching. It adds no format, casing, or lookup guidance beyond that single qualifier.

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 gives a specific verb ('Retrieve') plus a precisely scoped resource: normalized direct and ultimate accounting-consolidation parent identifiers reported to GLEIF for an exact LEI. The 'accounting-consolidation parent' framing implicitly separates it from the ownership tools (get_entity_owners, get_company_owners), but no sibling is named explicitly, so it stops short of full differentiation.

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?

'Use for public corporate-hierarchy research' gives clear positive guidance, and 'for an exact LEI' signals the prerequisite that a valid LEI must already be in hand (implying lookup_lei/search_lei first). It never states when not to use it or names the beneficial-ownership alternatives, so exclusion guidance is missing.

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