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

Annotations already cover readOnly/idempotent/destructive/openWorld, but the description adds substantial behavioral context beyond them: the walk-back is explicitly bounded ('never a bulk crawl'), the matching heuristic is disclosed, and it honestly reports `prior_filing_found: false` when no prior filing or a pre-structured-XML chain is found. This is exactly the kind of edge-case and failure-mode disclosure that structured annotations cannot carry.

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 content is front-loaded (verb and 13D/13G/A scope first, diffed fields next, mechanism and edge cases last) and every clause carries information. It is a dense single paragraph that runs long, but little of it is 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?

An output schema exists, so return-value explanation is unnecessary, and the description covers the key semantic nuances: bounded scan, identity-based matching, the false-fallback, and the free-text/structured-XML caveat. Nothing an agent needs to call this correctly 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 coverage is 100%, so both the issuer identifier and accession_number are already documented, including the note that an original 13D/13G yields no prior filing. The description restates the amendment framing but adds no syntax or format detail beyond what the schema provides. 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 verb+resource: 'find the SAME reporting group's prior filing in the chain and diff what changed', then enumerates exactly which fields are diffed (percent of class, aggregate shares, voting/dispositive power, Item 4 purpose). This clearly distinguishes it from the sibling sec_13d_filing/sec_13d_filings list/retrieve tools.

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?

It implies the triggering condition well: you supply one 13D/A or 13G/A amendment and it walks back the issuer's history. It explains the internal mechanism (matching on reporting-owner identity because EDGAR lacks a previous-accession link), which clarifies why this tool exists. It does not, however, name the sibling filing tools or explicitly state when to prefer this over simply fetching a filing.

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