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

Annotations already disclose destructive and idempotent behavior, so the bar is lower. The description adds the nuance that color can be cleared with null, which is not in the schema. However, it does not clarify what happens when only id is provided (since name and color are optional) or whether name and color can be updated simultaneously, leaving some ambiguity. No contradiction with annotations.

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 two sentences with zero fluff. It front-loads the core purpose (renaming and changing colour) and immediately adds the key nuance (null clearing) and the prerequisite for ID retrieval. Efficient and well-structured.

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 simplicity, the description covers the main operations and a key edge case (null color). It does not explicitly state that name and color are optional or that both can be updated together, but the output schema exists and annotations cover safety. The only notable gap is the behavior when only id is passed, which is minor. Overall, it is sufficiently complete for an agent to use correctly.

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 67%, but the description compensates by clarifying the source of id (list_tags) and the null-clearing behavior for color, which the schema does not describe. It also reinforces that name is for renaming and color for changing colour. This adds meaning beyond the schema, particularly for the color parameter.

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 a tag or changes its colour, with a specific verb and resource. It distinguishes itself from create_tag and delete_tag by focusing on modification, and the mention of clearing color with null adds 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?

The description provides a clear usage hint by stating 'Tag IDs come from list_tags', guiding the agent to first retrieve IDs. It implies usage for editing existing tags but does not explicitly exclude creation or deletion scenarios, nor does it mention alternatives like update_category. Still, the ID source is a practical guideline.

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