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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so safety is covered. The description adds only the 'No live execution model' caveat and the free-vs-full split; it does not disclose data freshness, coverage scope, or what 'blind spots' means behaviorally. That is useful but thin context beyond the 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?

It is short with no filler, but the structure is three telegraphic fragments rather than a front-loaded statement of action and return. Being terse at the cost of comprehension lands it at minimum-viable rather than strong.

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?

The tool is a simple read-only fetch with one optional parameter and no output schema. The description lists contents but never explains the shape of the return or what the headline row contains, leaving an agent to infer meaning from jargon. Adequate but with clear gaps for a tool that will be called blind.

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%, and the schema itself clearly explains that passing cik returns one filer's full FREE row instead of the all-filer headline. The description adds nothing about the parameter, so the schema does all the work — the correct baseline when coverage is complete.

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 names headline outputs ('effective positions, days-to-exit brackets, blind spots') for 'watched filers', which hints at an exit-feasibility screen, but it never states a plain verb/resource and relies on jargon ('watched-filer', 'blind spots'). It distinguishes itself from unwind_stress only by scope ('Full grids'), not by a clear purpose statement.

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 points to unwind_stress for full grids, giving one alternative, and notes 'No live execution model', which implies a lighter-weight screen. However, it never says when to choose this over other exit-related siblings such as exit_cost or trade_safety_exit_context, and there are no explicit exclusions.

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