redmine_delete_group

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

The description discloses critical behavioral traits: permanent deletion and the need for admin privileges. It also notes compliance with the REDMINE_MCP_READ_ONLY flag, which is important for agents respecting read-only modes. No annotations were provided, so the description carries the full burden and meets it well.

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 that pack essential information. The first sentence covers the action and constraints, and the second provides a behavioral flag. No wasted words.

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 description covers all necessary aspects for a deletion tool: what it does, who can use it (admin), its effect (permanent), and a behavioral flag. An output schema exists, so return values are not needed. It is fully complete for this tool's complexity.

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?

There is only one parameter (group_id), and the description does not explicitly mention it, but the tool name and action make it obvious that the parameter identifies the group to delete. The schema provides the type and title, so the description adds little value beyond that, but the context compensates. Given low schema coverage (0%), a 4 is justified because the intent is clear.

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 'Delete a group', providing a specific verb and resource. It distinguishes from sibling tools like redmine_create_group and redmine_update_group by its focus on deletion. The additional constraints 'admin only' and 'Permanent' add clarity.

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 includes a clear prerequisite ('admin only'), indicating when the tool is appropriate. It also notes 'Permanent' to warn about irreversibility. However, it does not explicitly mention when not to use it or suggest alternative tools for related operations (e.g., removing users from groups).

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