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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), yet the description adds substantial context beyond them: no auth/API key, no PII, safe to retry, concrete rate limits (60 req/min, 250 calls/day per IP), the {data, meta} envelope with its meta fields, and the critical 'meta.available false means unavailable or cache warming, never report as zero' rule.

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?

Purpose and prerequisite are front-loaded in the first two lines, and the behavioral/rate-limit block is well organized. It loses a point because the long inline enumeration of output fields (data.filing, data.associations, data.people, etc.) substantially duplicates the output schema, costing tokens without adding meaning.

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?

For a single-parameter read tool with an output schema present, the description supplies everything an agent needs: how to obtain the ID, what the result shape looks like, how to interpret meta (including unavailable/cache-warming), rate limits, and a verification caveat about machine-generated summaries.

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% and the single parameter is fully documented there, including format, length bounds, and the accession-number example. The description adds provenance ('get it from search_sec_filings') but 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 and resource (full detail for one SEC filing) and enumerates exactly what the detail contains: metadata/EDGAR link, machine-generated summary, associated mortgage entities and roles, people with titles and compensation, financial facts, and ownership rows. It is clearly distinguishable from the sibling search_sec_filings, which it names explicitly.

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 the explicit prerequisite and routing rule: 'Get the filing_id from search_sec_filings first,' which tells the agent it cannot discover filings here and must use the sibling search tool. It also states the reliability caveat 'Verify summaries against the linked filing before relying on them,' which is actionable guidance, not just context.

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