Tag task

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

The description claims idempotency, matching annotations, but omits the ability to remove tags (as shown in the schema). It also implies tags must start with 'claude-*', which is not enforced by the schema and may mislead agents about allowed tag patterns.

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 extremely concise, with no wasted words. However, it sacrifices completeness, leaving out critical details such as the remove capability. The brevity is a mixed blessing.

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 has three parameters and no output schema, the description should clarify both add and remove behavior. It only covers add, and the 'claude-*' restriction is unsupported. The agent cannot fully understand the tool's behavior from this description alone.

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?

With 0% schema coverage, the description must explain parameters. It partially covers the 'add' parameter by mentioning 'merge', but fails to describe the 'remove' array or the required 'id' parameter. The 'claude-*' prefix adds confusion rather than clarity.

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 the tool merges tags into a task, which is clear and distinct from sibling tools that handle assignment, attachment, creation, etc. The verb 'merge' appropriately conveys both adding and removing, but the mention of 'claude-*' tags adds unnecessary specificity.

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?

No guidance is provided on when to use this tool versus alternatives. While it is the only tag-related tool among siblings, the description does not clarify its role relative to others, such as task.update, or when to prefer task.tag over direct manipulation.

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