Kagan - AI Orchestration Layer

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool 'Clear all AI review verdicts,' which implies a destructive mutation, but doesn't specify whether this action is reversible, what permissions are required, or what happens to associated data. The description adds minimal context beyond the basic action, leaving key behavioral traits undocumented.

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 extremely concise with two sentences that directly state the purpose and usage guideline. Every word earns its place, and it's front-loaded with the core action, making it efficient and well-structured without any wasted 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 the complexity of a destructive mutation tool with no annotations, 0% schema description coverage, and no output schema, the description is incomplete. It lacks details on behavioral traits like side effects, permissions, or return values, and doesn't explain the parameter. For a tool that clears data, more context is needed to ensure safe and correct 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?

The description doesn't mention any parameters, and schema description coverage is 0%, with only one parameter ('task_id') documented in the schema without a description. The description doesn't compensate by explaining what 'task_id' refers to or its format, so it adds no semantic value beyond the schema. With 0% coverage and no param info in the description, the baseline is 3 as it doesn't contradict but doesn't enhance understanding.

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 states the action ('Clear all AI review verdicts') and the target resource ('for a task'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'review_set_criterion_verdict' or 'review_approve/reject', which also deal with review verdicts but in different ways.

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 provides clear context for when to use this tool: 'Call before starting a new review.' This gives practical guidance on timing. However, it doesn't mention when NOT to use it or explicitly compare it to alternatives among sibling tools, such as whether to use this versus 'review_abort_rebase' or 'review_set_criterion_verdict' in related scenarios.

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