Delete Tag

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

With no annotations, the description fully carries the transparency burden. It clearly discloses the cascading side effect of removing the tag from all documents and the behavior for ambiguous names. It lacks details on permissions or reversibility but covers the most critical aspects.

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, no wasted words. It front-loads the action and effect, then adds relevant nuance. Every sentence earns its place.

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?

The description explains the input and side effects but does not mention the return value or confirmation of deletion. Given no output schema and no annotations, a brief note on what the tool returns upon success would improve completeness.

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 50% (only 'tag' has a description). The description adds value by explaining that 'tag' accepts an id or name and that ambiguous names are rejected with candidates. However, 'workspaceId' is not mentioned in the description, leaving its purpose and optionality unaddressed.

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 'delete a workspace-level tag' which matches the tool name and specifies the resource type. It distinguishes itself from siblings like 'remove_tag_from_doc' by noting that it removes the tag from every document that references it, and also mentions a unique behavior for ambiguous names.

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 implies when to use this tool (to permanently delete a tag across the workspace) versus alternatives like 'remove_tag_from_doc' which only removes from a single document. However, it does not explicitly state when not to use it or provide direct comparisons.

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