update_tag

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

Discloses side effect 'changes apply to all assets using this tag' and optional parameters. No annotations provided, so description bears burden; it reasonably covers mutation behavior.

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?

Very concise: two-sentence summary followed by parameter list. Every sentence adds value 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?

With low complexity (3 params), no annotations, and existing output schema, the description sufficiently covers purpose, side effects, and parameter meaning. No gaps.

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?

Input schema has 0% description coverage; description compensates fully by explaining tag_id as UUID, name as optional new name, and color as hex format with 'Omit to keep current'.

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?

Description clearly states 'Update a tag's name or color' with a specific verb and resource. The side effect mentions global application, distinguishing it from create_tag or delete_tag.

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 explicit when-to-use or when-not-to-use guidance. The description implies modification context but lacks direct comparison to sibling tools like create_tag or delete_tag.

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