Can the watched books exit? (free)

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, and the description strengthens these by explaining that the measure is display-only on frozen grids, that 13F filings exclude shorts/options, and that all numbers are floors. It also discloses non-obvious output behavior such as reporting counts as bands rather than points and returning one of NO_CALL / CALL / EQUITY_EXHAUSTED.

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 dense and information-rich but not especially concise or scannable. Important 'when to use' guidance appears near the end, and the parenthetical explanation about why counts are bands adds interpretive detail beyond what is needed for tool selection/invocation. The 'Not investment advice' tag is also non-essential.

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 there is no output schema, the description does a good job compensating by enumerating the main output components: effective position count, whole-book days-to-exit, the margin grid states, and the default versus per-filer row behavior. It also conveys the tool's limitations. A structured field-by-field output contract would make it fully complete.

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?

The input schema has 100% coverage of its single optional cik parameter, including the meaning of omitting it versus passing it. The description's 'Default is the per-filer headline; pass cik for one filer's full free row' mostly restates the schema rather than adding new parameter-level semantics.

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 identifies a specific verb and resource: it measures whether a watched 13F filer's book can exit by reporting position counts, days-to-exit bands, and a leverage/shock/maintenance-margin grid. It also explicitly ties the tool to a concrete question ('whether a fund's book could exit'), which distinguishes it from generic exit-cost or liquidity 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?

The description gives an explicit use case: 'Use when asked whether a fund's book could exit, or what the Aschenbrenner failure mode looks like in a current filing.' It also notes important exclusions via 'Display-only measure on frozen grids' and '13F sees no shorts or options, so every number is a floor.' It does not name sibling tools as alternatives, so it stops just short of the top score.

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