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

Annotations already declare it read-only, idempotent, and non-destructive. The description adds valuable behavioral context beyond those: it returns only counts and the most recent rows of each filing type, and it applies different lookback windows (90 days vs. 1 year). 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 main sentence is dense and front-loads the tool's identity ('One-call SEC filing overview') before listing specifics. The second sentence is slightly redundant with 'overview' but adds the user-intent context 'for quick due diligence,' so it earns its place.

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-only summary tool with a rich input schema and an output schema, the description is complete. It states the data sources, time ranges, output shape (counts and most recent rows), and purpose, so an agent has enough to select and invoke it correctly.

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 baseline applies. The description adds the 'US-listed company' constraint, which is useful, but it does not materially elaborate on accepted ticker/name/CIK values beyond what the schema already states. 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?

Description names a specific verb/resource ('SEC filing overview') and enumerates exactly what it covers: Form 4, 8-K, and Schedule 13D/G filings with time windows. It is clearly differentiated from focused siblings like insider_trades, insider_8k, and insider_13d by being a one-call aggregate.

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 a clear context ('Answers what has been happening at a company lately, for quick due diligence'), implying this is an initial overview rather than a deep dive. However, it never explicitly names alternatives or says when NOT to use this tool, leaving the agent to infer routing from sibling names alone.

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