remove_tag

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

Annotations already indicate destructiveHint=true. The description adds that tasks are preserved and child tags are cascade-deleted, which are important behavioral traits beyond the annotations. However, it does not mention permanence or potential side effects like affecting tasks referenced by the tag.

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 two sentences long, both essential and without redundancy. It efficiently conveys the core purpose and key behavioral notes.

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?

While the description explains the deletion behavior, it does not mention what the tool returns (e.g., success message, deleted tag object) nor handle edge cases like non-existent tags. For a destructive tool with no output schema, this leaves some ambiguity.

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 description coverage is 100%, with both id and name parameters already described. The tool description does not add any new information beyond what the schema provides, so it meets the baseline without enhancement.

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 deletes a tag from OmniFocus, specifying that tasks are not deleted and child tags are also removed. This distinctively separates it from sibling tools like remove_item or edit_tag.

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 provides useful context that removing a tag only removes it from tasks and deletes child tags, but lacks explicit guidance on when to use this tool versus other tagging tools or alternatives for removing tags from individual tasks.

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