deleteTagGroup

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

Goes beyond annotations: emphasizes permanence ('cannot be undone via API'), describes impact on child tags (orphaning), and states no soft-delete. Contradicts none of the annotations (destructiveHint, idempotentHint, etc.) and adds crucial behavioral context.

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?

Efficiently structured with bold headings, each sentence earns its place. Front-loaded with main action, no redundant phrases. Approximately 100 words covering purpose, usage, behavior, parameters, and return format.

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?

Completely covers a simple delete operation: describes action, side effects (orphaned children), irreversibility, required parameter, return format. No output schema needed; description provides sufficient context. Sibling tools are many, but this description uniquely addresses its role.

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?

With 0% schema description coverage, the description carries full burden but only notes that 'id' is required and mentions it in the return format. Does not explain what 'id' represents (e.g., the ID of the tag group to delete). Schema itself is minimal (integer, required), so description adds marginal value.

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?

Clearly states verb+resource: 'Delete a tag group' and specifies permanent deletion. Differentiates from siblings like deleteTag and updateTagGroup by explicitly naming the resource and providing a 'See also' link to the update alternative.

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?

Provides explicit use case: 'removing a group - child tags orphan; delete or re-group them first.' Warns about destructive nature and need for user confirmation before bulk use. Suggests updateTagGroup as alternative, fulfilling when-to-use and when-not-to-use guidance.

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