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

Annotations only declare readOnlyHint and openWorldHint; the description adds genuinely useful behavior beyond them: a concrete price ($0.006 USDC over x402), that failed calls are free, and a two-step quote-then-pay handshake. It stops short of stating rate limits, latency, or result shape, but the cost/payment disclosure is substantial for a paid tool.

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?

Two short paragraphs, front-loaded with what is returned and followed by the commercial mechanics. Every sentence carries information the agent needs — scope, contents, price, failure cost, and the quote flow — with no 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 5 parameters, zero required, no output schema, and a read-only open-world profile, the description does the work an output schema would have done by listing the returned sections and the financial time ranges. The one real gap is that it never clarifies its relationship to the sec_company/sec_financials siblings.

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 80%, so the schema already documents cik, ticker, form, filings, and payment. The description adds no parameter-level syntax or defaults beyond the schema, and the one detail it does touch (omitting payment yields a quote) is already in the payment field's schema description. Baseline 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 names a specific verb and resource ("Get a one-call snapshot of a US public company from SEC EDGAR") and enumerates the payload: profile, recent filings with links, and named financial metrics. It never distinguishes itself from the closely related siblings sec_company and sec_financials, so an agent cannot tell from the text alone why it should pick this aggregator over those granular tools.

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?

Usage is implied by "one-call snapshot" (use when you want everything at once) and the payment protocol is spelled out procedurally. However, there is no explicit when-to-use/when-not statement and no routing to the sibling tools that appear to cover the same SEC data, which is the most likely agent confusion here.

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