Manage tag

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

With no annotations, the description bears the full burden. It only discloses that delete uses Preview/Apply, omitting side effects, confirmation requirements, reversibility, and behavior for other operations. The mismatch between 'reorder' in the description and 'move' in the schema enum adds ambiguity.

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 efficient sentence that wastes no words. However, the terminology inconsistency ('reorder' vs 'move') slightly reduces structure clarity, and the terse format could be improved with operation-specific details.

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?

This is a complex tool with 7 parameters, nested objects, multiple operations, and a preview/apply mode. The description fails to explain the meaning of mode, confirmation_token, orders, patch, or tag_ref, making it insufficient for correct invocation without external documentation.

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% for 7 parameters, and the description provides no parameter-level explanations. It does not describe tag, patch, orders, tag_ref, mode, or confirmation_token semantics, leaving the agent to infer everything from the schema itself.

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's actions: 'Create, update, hide, unhide, reorder or delete tags.' This is a specific verb+resource statement that distinguishes it from sibling tools like list_tags (listing) and manage_tag_group (group management).

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 operation list implies usage for tag CRUD and reordering, but no explicit guidance is given about when to use this tool versus alternatives, nor does it explain the preview/apply flow for delete. The note 'Delete uses Preview/Apply' hints at a two-phase pattern but fails to clarify when preview vs apply should be used.

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