mixer_group_delete

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

No annotations are provided, so the description must carry the behavioral disclosure burden. It does disclose a useful side effect: objects routed through the group will need re-routing afterwards. However, it does not explicitly state permanence, irreversibility, failure conditions, or return behavior, which would be valuable for a destructive tool.

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 compact and well structured: a one-line purpose, a crucial warning, and the argument definition. Every sentence provides necessary information, and there is no fluff or redundancy.

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?

For a simple one-parameter delete tool with no output schema and no annotations, the description is largely complete: it states the action, the target format, and an important consequence. It could additionally note that the delete is permanent or irreversible, but the warning about re-routing covers the most material side effect.

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 schema only defines target as a required string, with 0% description coverage. The description compensates fully by documenting the parameter as 'Group path or {guid}', adding critical semantic meaning beyond the schema. This covers the only parameter completely.

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's action with a specific verb and resource: 'Delete a mixer group.' It is unambiguous and distinguishes itself from sibling tools like mixer_group_rename, mixer_group_info, and mixer_group_route, which perform different operations on mixer groups.

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 usage is implied by 'Delete a mixer group' and the warning about objects needing re-routing, but there is no explicit guidance on when to choose this tool over alternatives such as utility_delete, nor any conditions or exclusions. No alternative tools are named.

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