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

Annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false, so the safety profile is covered structurally. The description adds nothing about what actually changes — whether 'value' replaces the existing label text, whether colorHue is reset, or whether the change is reversible.

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?

A single short sentence with no filler, but it is under-specified rather than truly concise — brevity here comes at the cost of the information an agent needs.

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?

A destructive mutation with no output schema, zero parameter documentation, no usage guidance, and no description of effects leaves an agent without enough to invoke it correctly or predict consequences.

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% and the description mentions no parameters. The required labelId, plus value and colorHue, are completely undocumented anywhere; the loose phrase 'for an organization' only vaguely gestures at orgId.

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?

States a verb ('Update') and a resource ('process tags for an organization'), but calls labels 'tags' while the tool name and every sibling use 'Label', creating a terminology mismatch. It also fails to distinguish itself from close siblings such as createClarityProcessLabel, deleteClarityProcessLabel, and unlinkClarityProcessLabels.

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 when-to-use guidance, no prerequisites, and no mention of alternatives. The description does not tell an agent when updating a label is appropriate versus assigning, unlinking, or deleting one.

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