auto_review_trigger

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

Beyond annotations, describes conditional firing and force skip. Missing details on what happens when conditions not met (e.g., no rich thread). No contradictions 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 focused paragraphs, no wasted words. Could benefit from bulleted param descriptions.

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?

Covers main behavior and force use, but leaves focus unexplained. Output schema exists but description gives no output hint, though partially offset by schema.

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?

Explains force parameter well but does not describe focus parameter (default 'combined'). With 0% schema coverage, more param detail needed.

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?

Clearly states it checks counters and close-thread state then fires review_thread(mode='auto'). Distinguishes use case for skill_nudge/skill_hint from manual thread selection. Could more explicitly differentiate from review_thread sibling.

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 advises use after skill_nudge or skill_hint, and describes force=True scenario. No explicit when-not-to-use, but implication is clear.

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