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

Annotations already establish that the tool is read-only, idempotent, non-destructive, and open-world. The description adds useful behavior beyond that by disclosing the paid x402 HTTP access model and $0.02 cost per call, though it remains unclear what the tool actually returns and whether payment is handled automatically.

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 only two sentences and front-loads the domain before the payment detail. It is concise, though the phrase 'returns how to call it' introduces ambiguity rather than useful clarity.

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 four-parameter lookup tool with no output schema and no parameter descriptions, the definition is incomplete. It leaves unresolved whether the tool returns registration data or only invocation instructions, and it does not explain how the optional identifiers are matched or prioritized.

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 schema has four parameters with 0% description coverage, and the description does not define cik, lei, name, or ticker. It hints at LEI and SEC EDGAR, which loosely maps to lei and cik, but gives no meaning for name or ticker or for how identifiers should be combined.

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 identifies the domain as LEI records and SEC EDGAR registration for a company, but then says the tool 'returns how to call it,' which blurs whether it retrieves company data or only payment/calling instructions. It does not clearly differentiate itself from siblings such as company_financial_facts.

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?

There is no guidance on when to use this tool versus alternatives, nor on how to choose among cik, lei, name, and ticker. The only operational context is that calls are paid over HTTP with x402.

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