Delete group

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

The annotations already declare destructiveHint: true and idempotentHint: true, covering the safety profile. The description adds little beyond restating 'Deletes an existing group' and providing the API endpoint. There is no contradiction with annotations, but no substantial additional behavioral context is disclosed.

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 short and front-loaded, but contains redundancy: 'Delete group' and 'Deletes an existing group' convey the same meaning. The API endpoint is useful. Overall it is concise and easy to scan, but the redundancy prevents a perfect score.

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 delete operation with one parameter and strong annotations, the description is mostly complete. It lacks details about return values or error handling, but no output schema exists and the annotations cover the destructive nature. The endpoint adds useful context, making it adequate for low 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?

The input schema fully describes the only parameter (id) with a clear description. The tool description does not add any further parameter semantics, but schema coverage is 100%, so the baseline of 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 identifies the tool's function: deleting a group. It specifies the resource ('group') and action ('delete'), and includes the exact API endpoint. This distinguishes it from sibling tools like deleteDevice and deleteTag.

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 implies the use case: when you need to delete an existing group. It provides clear context without explicitly excluding alternatives like removeGroupDevices, but for a straightforward delete operation this is sufficient. No explicit when-not-to-use guidance is given, so it doesn't reach a 5.

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