delete_contact_group

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

The description merely restates the action without adding any behavioral context. Annotations already flag destructiveHint and idempotentHint, but the description adds no extra details such as cascading effects, permission requirements, or irreversibility beyond what annotations provide.

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 a single short sentence, which is concise. However, it is under-specified and adds little value over the tool name, making it borderline between appropriate minimalism and under-specification.

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, the description is minimally sufficient. It does not mention irreversible consequences, effects on associated contacts, or return values (no output schema exists), so some additional context would improve 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?

The input schema fully documents the single parameter contact_group_id with a description, achieving 100% schema coverage. The description itself adds no additional semantic meaning beyond what the schema already provides, so the baseline score 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 'Delete a contact group' clearly states the verb (delete) and the resource (contact group). It is specific but does not differentiate from other delete tools, so it falls short of a 5.

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 guidance on when to use this tool versus other contact-related operations, nor any mention of prerequisites (e.g., whether the group must be empty) or alternatives. The description provides no usage context.

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