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

Annotations cover the safety profile (readOnly, idempotent, non-destructive), and the description adds critical behavior the annotations cannot: this is a paid x402/MPP endpoint at $0.008 per call, it returns a request descriptor rather than the data itself, and bad input is refused before charging. That extra step is essential to invoking it correctly.

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, front-loaded with the 'Use when' trigger, followed by the return/payment mechanics and then the sibling routing. Dense but every sentence carries load; the payment-flow sentence is long but necessary.

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 no output schema, the description compensates by explaining that the response is an x402 request descriptor containing the response schema and an example, plus the URL and price. It covers the full invocation flow, though it does not describe pagination or what 'key financials' actually includes.

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 documents cik, ticker, form, and limit. The description restates 'by ticker or CIK' but adds no format or interaction detail beyond what the schema provides, so the baseline 3 applies.

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?

States a specific verb and resource – retrieving 'SEC EDGAR filings and key financials' – scoped by ticker or CIK, and names the sibling (sec_filings_batch) it is not. An agent can tell exactly what this returns and how it differs from the batch variant.

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?

Opens with an explicit 'Use when you need...' trigger and routes multi-company lookups to sec_filings_batch. It lacks an explicit when-not clause (e.g. non-US companies), but the usage context is clear enough to select correctly.

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