Remove Tag

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and idempotentHint=true, so the safety profile is covered. The description adds minimal behavioral context beyond 'remove one tag reference,' such as clarifying that only the reference is removed, not the tag. It does not mention the confirm parameter or potential side effects, but annotations carry much of the burden.

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 concise sentence that is immediately action-oriented and easy to parse. It contains no filler and effectively captures the core function.

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?

Given the tool's complexity and the presence of a confirm parameter with no documentation, the description is incomplete. An agent would not know whether confirm must be set to true to execute the removal, nor what happens if the tag reference does not exist. The description and schema together leave out essential invocation details.

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%, so the description must compensate, but it does not explain any of the four parameters (tag_id, confirm, entry_id, bundle_id). The confirm parameter is particularly ambiguous—it is a boolean with a default, yet neither the description nor schema clarifies its purpose. The description adds no meaningful parameter-level information.

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 states 'Remove one tag reference from an entry,' which includes a specific verb ('remove'), a resource ('tag reference'), and a context ('from an entry'). It clearly distinguishes this from sibling tools like bundled_delete_tag (which likely deletes the tag definition) and bundled_apply_tag (which adds a reference).

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 no guidance on when to use this tool versus alternatives, nor does it mention exclusions or prerequisites. While the name and verb imply the use case, there is no explicit mention of related tools such as bundled_apply_tag or bundled_delete_tag, leaving the agent to infer the appropriate context.

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