Recheck Scans

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

Annotations are sparse but description adds: no new crawl fee, only checker cost; returns count of queued scans. No contradiction with 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?

Two efficient sentences, first explains function, second adds cost detail. No superfluous text.

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 simple parameters and no output schema, description adequately explains return value (count) and scope (completed scans). Sufficient for agent usage.

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 covers parameters fully (100%). Description adds important constraint that only completed scans are eligible, which is not in schema. Also clarifies cost context.

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?

Description clearly states the tool re-runs the checker pipeline on completed scans, which is distinct from creating new scans. It gives specific use cases like after policy updates, and mentions cost implications.

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?

Explicitly says when to use (after updating policies or custom rules). Does not explicitly mention when not to use, but context implies it's for re-evaluation only, not new scans.

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