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

Goes well beyond the readOnlyHint annotation: discloses pricing and x402 terms, the free-ticker set, the not_covered outcome for uncovered tickers, and critically that the ZIP bytes themselves are only served over HTTP routes rather than returned inline. These are exactly the operational facts an agent needs before invoking.

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-loads the core deliverable, then layers contents, pricing, and edge cases. Nearly every clause carries information, though the middle sentence is dense and could be split for readability.

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 carries the return-shape burden and does reasonably well: it names the manifest, workbook, quarterly-card pointer, the payable URL, and the not_covered sentinel. Coverage of what a successful vs uncovered response looks like is sufficient for correct invocation.

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 ticker and slug semantics. The description adds little parameter-level detail beyond the manifest-listing default that the schema also states, so 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: one company's SEC 10-K/10-Q delivered as a ZIP, with an explicit inventory of contents (HTML, workbook, manifest, quarterly-card pointer). An agent can tell what it gets. It does not, however, explicitly contrast itself with the closest sibling, check_10q_coverage, so it falls short of a 5.

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?

The description gives useful selection context (free tickers AMD/MRVL/AVGO/MRCY, paid bundles at $0.05, not_covered when nothing exists) but never states when to choose this over check_10q_coverage or get_line_item_trajectory. Usage is implied by resource type rather than stated as a rule.

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