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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely new behavior: per-company fault isolation ('one failure does not fail the batch') and the checkpoint-return contract that drives the next run.

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?

Three short sentences, zero filler, front-loaded with the core action, then isolation guarantee, then return contract. Each sentence 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 9-parameter tool with a nested checkpoints object and no output schema, the description covers the batch semantics and return contract but leaves most tuning parameters and the shape of per-issuer results (successful vs failed companies) undiscussed. Adequate but with real gaps.

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 67%, so much is already documented. The description adds the 10-issuer ceiling and the notion of checkpoint round-tripping, but says nothing about item, forms, limit, history, maxNewFilings, or comparisonLimit, leaving the higher-cost tuning knobs unexplained.

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 and resource ('Run the same checkpointed disclosure-change monitor') plus a bounded scope ('across up to 10 issuers'). It implies a batch counterpart to the singular check_disclosure_changes sibling but never names it, so differentiation is left to inference.

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 'up to 10 issuers' framing and 'return updated checkpoints for the next agent run' imply the multi-issuer, repeated-monitoring use case. However, it never states when to prefer this over check_disclosure_changes or any other sibling, nor any exclusions.

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