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

The description adds significant behavioral context beyond the annotations (readOnlyHint, destructiveHint). It explains the two distinct result structures (one metadata object vs. a filings list), details the document_type and announcement_type fields, and describes how parameter combinations affect behavior. No contradictions 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 front-loaded with the main purpose and then systematically explains modes and field details. It is slightly verbose but every sentence adds value. The structure is logical and easy to parse.

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 the complexity (two modes, multiple parameters, no output schema), the description is remarkably complete. It covers all parameter combinations, result structures, field meanings, and enum values. The agent has sufficient information to decide when and how to use the tool.

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?

With 60% schema description coverage, the description compensates by explaining the effect of omitting ticker/company, the role of filing_registry, and the meaning of document_type values including FCA press subtypes. This adds value beyond the schema, though ticker and company parameters lack explicit descriptions.

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 returns the latest filing metadata for a company or ticker and explains both modes (with company/ticker and without). It is specific about the verb and resource, but does not explicitly differentiate from sibling tools like get_filing_toc or list_filings, so a 4 is appropriate.

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 provides explicit guidance on when to use each mode: with ticker/company for a specific company, or omit them for newly ingested filings. It also advises omitting filing_registry in the latter mode to include both SEC and FCA. This is clear contextual guidance, though it does not list alternative tools or when to avoid.

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