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

With no annotations, the description carries the behavioral disclosure burden, and it does well: it discloses that the tool is paid (1.0 USDC per call), that it returns a payment challenge unless already settled, and that analysis is derived from attested facts only. This is significant practical behavioral context beyond the schema.

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 compact and front-loaded with the core purpose, but it contains marketing-like details such as '$1+ moat product (CEO 12B #1; census 2026-09-06)' that do not help an agent select or invoke the tool. The pricing and payment-challenge sentence is valuable, but the product boast is unnecessary.

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?

The description covers the endpoint, price, payment challenge, and data contents, which is strong for a paid API with no output schema. However, it does not describe the shape of the successful report response or the settlement flow in enough detail, leaving some ambiguity about what the agent will receive after payment is resolved.

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 parameters are already well documented. The description does not add meaning beyond the schema, such as how cik and ticker interact or the meaning of focus values, so a baseline score of 3 is appropriate.

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 clearly states the tool produces an investment-grade EDGAR company report with attested SEC XBRL fundamentals and machine-formatted analysis, so an agent can tell what resource is being acted on. It does not explicitly contrast itself with the sibling edgar_financials, but the 'attested' and 'analysis' framing differentiates it enough for most selection scenarios.

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 edgar_report versus edgar_financials or other siblings. The description implies use for investment-grade attested reports but gives no explicit when/when-not conditions or alternative routing.

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