deleteTag

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

Adds beyond annotations: orphaning of rel_tags, no undo, no soft-delete, return format. Annotations already indicate destructive, description elaborates.

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?

Well-structured with bold section headers. Every sentence adds value. No fluff, front-loaded with action and caution.

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?

Covers action, consequences, required param, return shape, and use cases. No gaps given simplicity and existing annotations.

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?

Schema coverage 0%, but single param 'id' is simple integer. Description states 'Required: id' and contextually clarifies it's the tag ID. Adequate but no extra detail beyond schema.

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 'Delete a tag' and 'Permanently delete a tag record by ID.' Distinguishes from siblings like updateTag by specifying 'remove entirely.'

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?

Explicitly provides when to use ('removing a tag entirely'), when not ('no soft-delete'), and alternative (updateTag). Warns about intent confirmation for bulk use.

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