manage_reviewer_groups

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

The description indicates that the 'delete' action removes a group, which is a destructive operation. However, the annotations set destructiveHint=false, directly contradicting the description. Additionally, the description provides no behavioral context about side effects (e.g., permanent removal, impact on assigned reviewers) beyond the action names. This is a serious inconsistency.

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: two sentences with no redundant words. It front-loads the purpose and then lists actions efficiently. Every sentence adds value without waste.

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 6 parameters and no output schema, the description covers the core operations but omits important context: error behavior (e.g., duplicate group name on create, non-existent group on delete), permission requirements, and whether changes are immediate or reversible. For a management tool with destructive actions, this lacks necessary completeness.

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 coverage is 100%, so the description adds limited new meaning. It clarifies that 'reviewers' and 'description' are applicable only for the 'create' action, which is already stated in the schema descriptions. The description does not further explain parameter semantics, such as format constraints or defaults for 'project'. Baseline 3 is appropriate.

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 manages reviewer groups for a repository and enumerates the supported actions (create and delete). While it specifies the verb and resource, it does not explicitly differentiate from sibling tools like list_reviewer_groups or manage_review, but the name and actions make the purpose distinct enough.

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?

No guidance on when to use this tool versus alternatives. There is no mention of prerequisites, error handling, or when not to use it (e.g., if a group already exists or does not exist). The implied use case is for creating or deleting reviewer groups, but without explicit context, the agent may misuse it.

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