update_tag

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

The description adds value beyond schema by noting that renaming updates everywhere and only provided fields change. However, with no annotations, it does not cover auth needs, response behavior, or potential side effects like color propagation.

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?

Two concise sentences, front-loaded with purpose. Every word is meaningful without redundancy.

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?

Adequate for a simple update tool, but missing details on return values or error states. No output schema, so description could be more complete for mutation operations.

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 coverage is 100%, so the description only reinforces that only provided fields change, which is already implied by optional parameters. No additional meaning beyond schema.

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 renames or recolours a tag, with specific verb and resource. It distinguishes from siblings like create_tag and delete_tag by focusing on update operations.

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 (to rename/recolour a tag) but does not explicitly state when not to use or compare to alternatives. Context is clear given sibling set includes create and delete.

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