delete_tag

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

With no annotations provided, the description carries the burden of behavioral disclosure. It clearly states the destructive cascade ("removes from all items") and project scope, which is valuable. It does not mention permanence or permissions, but the core behavior is adequately disclosed for a simple delete tool.

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 a single sentence, front-loaded with the verb, and contains no unnecessary words. It is appropriately sized for the tool's simplicity.

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 1-parameter delete tool with no output schema, the description covers the essential action and its global effect. It could add a note about irreversibility or error handling, but the current description is sufficient for most use cases.

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?

The schema has one parameter (tag_id) with only the trivial description 'tag_id parameter'. The tool description does not add meaning beyond the schema; it is obvious that tag_id identifies the tag to delete. With 100% schema coverage (even if minimal), the baseline is 3.

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 uses a specific verb "Delete" with a clear resource "a tag from current project" and adds the scope "removes from all items". This distinguishes it from siblings like remove_tag (which likely removes a tag from a single item) and update_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 clear context that this tool operates on the current project and has a global effect (removes from all items), implying it is for project-level tag deletion rather than item-level removal. However, it does not explicitly name alternative tools like remove_tag or specify when not to use it.

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