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

With no annotations, the description carries the full burden of behavioral disclosure. It does reveal key aspects: it is a read-only retrieval, includes a tamper-evident trust envelope (content hash, content-trap scan, provenance), and costs $0.05 per call. However, it does not describe the response format, error behavior, rate limits, or any side effects. This leaves significant gaps for a tool with no output 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 a single sentence with compact parenthetical details (forms, trust envelope, cost). It front-loads the primary purpose and avoids redundant phrasing or filler. Every piece of information earns its place, making it highly efficient.

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?

Given a single parameter and no output schema, the description covers the essential usage (what to retrieve and that there is a cost) but omits critical details such as the response format, pagination, or how the trust envelope is delivered. It does not explicitly state that the task parameter should contain the ticker or CIK, though it is implied. The description is adequate but not fully self-sufficient.

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?

The schema parameter 'task' has a generic description ('Task/query text for this SKU') that does not explain how to specify the ticker or CIK. The tool description adds context by stating the purpose (ticker or CIK) but does not clarify the expected format of the task query (e.g., 'AAPL' vs '0000320193'). With 100% schema coverage but minimal parameter detail, the description adds some value but fails to fully compensate for the lack of parameter guidance.

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 retrieves recent SEC EDGAR filings (10-K/10-Q/8-K) for a ticker or CIK. The verb 'retrieval' and specific resource make the purpose unambiguous, and it is distinct from sibling tools like data.business-registry or oracle.price-feed. The mention of the trust envelope and public-domain source adds helpful context without obscuring the core function.

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 implies usage for SEC EDGAR filings but does not explicitly state when to use this tool versus alternatives. It mentions the target audience (ticker/CIK) and the forms covered, but there is no mention of exclusions (e.g., 'use for non-SEC data use data.business-registry') or explicit conditions. The guidance is implied rather than explicit, so it falls short of a 4.

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