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

The description adds context about the multi-reviewer process and moderator synthesis, which is beyond the annotations. However, it does not disclose important behavioral traits such as asynchronous completion via webhook or external processing, leaving gaps that the schema only partially covers. 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?

The description is only two sentences and immediately communicates the tool's nature as a 'Code review council,' with no filler. It is well-structured and front-loaded.

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?

The tool's complexity (optional focus, language, webhook, thinking level) is not addressed in the description, and no output schema exists to explain return values. While the schema compensates for parameters, the description leaves ambiguity about how results are delivered, especially with the webhook option. Still, the core purpose is clear enough for a basic invocation.

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?

All five parameters are fully described in the input schema (100% coverage), so the description need not repeat them. The description adds no parameter-specific semantics, but the schema's descriptions for 'code', 'focus', 'language', 'webhook_url', and 'thinking_level' are sufficient.

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 tool analyzes code using multiple specialized reviewers and synthesizes findings, with 'analyze your code' as the specific verb+resource. It distinguishes itself from siblings like 'consult-council' by framing itself as a code review council with distinct roles.

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?

There is no explicit guidance on when to use this tool versus alternatives such as 'consult-council' or 'debug-issue.' The description only implies usage for code review through the 'Code review council' framing, giving context but not exclusions or alternatives.

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