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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, covering the safety profile. The description adds valuable behavioral context beyond those: no authentication required, the specific data source (data.sec.gov / EDGAR), and that it returns both filings and an entity profile. No contradiction with annotations.

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 densely informative yet concise: five sentences each add distinct value (purpose, content, filter option, return fields, prerequisite/source). It is front-loaded with the core action and avoids redundant 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?

For a 3-parameter tool with an existing output schema and strong annotations, the description is complete: it covers purpose, return contents, parameter prerequisites, data source, and authentication status. Nothing an agent needs to decide to call this tool is missing.

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%, with each parameter (cik, limit, form_type) already well-documented in the schema. The description adds only marginal extra meaning by reiterating the CIK prerequisite and mentioning optional form_type filtering, so the 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 states a specific action ('Get a company's recent SEC filings'), names concrete filing types (10-K, 10-Q, 8-K, proxy statements, insider forms), and lists exactly what is returned (entity profile fields, filing date, accession number, document URL). It clearly differentiates from sec-edgar.company_lookup by stating the CIK prerequisite and from financial-data tools by focusing on filings plus profile.

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 clear context: it requires a CIK from sec-edgar.company_lookup, supports optional form_type filtering, and describes the response contents. It does not explicitly name alternatives or say when NOT to use this tool (e.g., versus finance.edgar.filings or sec-edgar.financials.concept), but the prerequisite and scope make usage fairly unambiguous.

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