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 the non-obvious behaviors the annotations cannot: the call does not return data but returns a paid x402 request recipe (endpoint, $0.08 per call, response schema + example), the caller must POST it with an x402 or MPP client, and invalid input is refused before any charge. That is exactly the extra context an agent needs to avoid mis-invoking it.

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?

Front-loaded with the usage condition, then the return semantics, pricing, and fallback. Four sentences, each carrying distinct information; slightly dense with the endpoint/client mechanics but nothing is wasted.

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?

No output schema exists, and the description compensates by explaining what actually comes back (an x402 request payload plus response schema and example), the price, and the pre-charge validation behavior. An agent has everything needed to call it correctly and route single-company work to sec_filings.

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 companies/form/limit, including the 1-10 bound and duplicate removal. The description restates 'up to 10 tickers or CIKs' but adds no syntax or format detail beyond the schema, 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+resource+scope: 'recent SEC EDGAR filings for several US public companies at once: up to 10 tickers or CIKs in one POST.' It also explicitly names the sibling it is not ('For one company use sec_filings'), so an agent can distinguish it from sec_filings without opening either schema.

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?

Gives an explicit trigger ('Use when you need ... several US public companies at once'), the batch-size constraint, and a named alternative ('For one company use sec_filings'). When/when-not/alternative are all present.

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