tag_delete

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

With no annotations, the description fully carries the transparency burden. It discloses irreversibility, deletion of children, removal from tasks, side effects (writes to OmniFocus, sets meta.syncPending), and return value.

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 compact (4 sentences) with key information front-loaded (irreversibility, action). Every sentence adds value without redundancy, including an example call.

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?

Despite no output schema, the description explains the return value (deleted tag ID) and side effects. It is comprehensive for a destructive tool given the context signals and sibling tools.

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 is 100% for the single parameter 'id,' and the description merely echoes the schema's note to get the ID from tag_list. No additional semantic meaning is added beyond the schema, meeting the baseline for high coverage.

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 'Hard-delete a tag from OmniFocus' with the verb 'hard-delete' and specifies the resource (tag). It distinguishes from the sibling tool 'tag_set_status' by noting its irreversibility and recommending the alternative for preserving history.

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 explicit guidance: 'Prefer tag_set_status with status='dropped' to preserve history' and instructs users to 'Get the tag ID from tag_list,' offering clear when-to-use and when-not-to-use context.

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