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

Annotations cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds substantial beyond-schema behavior: every response states the coverage window, values are quarter-end as-of and up to ~45 days stale, only long US 13(f) positions are covered, and not_held vs not_found are semantically distinguished.

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?

Front-loaded with the core check, followed by the four outcome states and then the Rule-2 constraints. Dense but every clause carries information; the status enumeration is slightly heavy but justified by the tool's ambiguity-prone semantics.

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?

No output schema exists, yet the description effectively documents the return contract by naming each status value, and it discloses coverage-window and staleness caveats. For a 6-parameter verification tool this is complete enough to call 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 is 3. The description reinforces the issuer_name/cusip vs filer matching rule and the 'ticker is never guessed' constraint, but this overlaps the schema's own parameter descriptions rather than adding new syntax or format guidance.

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 (verify/check) and resource (a fund's 13F holding of an issuer as of a quarter) and explicitly distinguishes itself from sibling verify_* tools by tying to SEC Form 13F-HR. The distinct outcome semantics (held/not_held/not_found/out_of_coverage) make it unmistakable.

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 use case is clear: check whether a filer held an issuer in a given quarter, with explicit coverage-window routing via out_of_coverage and the not_held vs not_found distinction. It does not name sibling alternatives or state exclusions explicitly, so it falls short of a 5.

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