delete_tag

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It explicitly states the destructive effect: "Removes the tag and all its associations with tasks." It also discloses the return value (confirmation with tag name and affected task count). It does not explicitly mention irreversibility, but "delete" inherently implies it, and the description covers the main side effect.

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 concise and well-structured: purpose statement, side-effect detail, args, and returns. Every sentence adds value with no verbosity or redundancy. It is appropriately front-loaded with the core action.

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 tool with one parameter and no annotations, the description covers all necessary aspects: the operation, the side effect (removing associations), the parameter, and the return value. The output schema exists but the description independently summarizes the return, providing sufficient context for an agent to invoke the tool correctly.

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 0%, meaning the input schema only provides a type and title for tag_name. The description compensates fully by stating "tag_name: Name of the tag to delete," adding semantic meaning beyond the schema. This is a single-parameter tool, and the description makes the purpose of that parameter explicit.

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 opens with a clear verb+resource: "Delete a tag from the system," and further specifies that it removes the tag and all associations with tasks. This distinguishes it from siblings like set_task_tags (which manages task–tag associations) and delete_task, making the tool's purpose unambiguous.

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 clearly implies when to use this tool (permanently remove a tag and its associations) and provides the key context that all task associations are removed. It does not explicitly name alternatives or exclusions, but the sibling list contains no other tag-deletion tool, so the intended usage is clear. A minor gap is not mentioning that to only detach a tag from a task, one should use set_task_tags.

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