label-update

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

With no annotations, the description must fully disclose behavior. It only says 'Updates a label', indicating a write operation, but omits details like whether the operation is idempotent, what happens on invalid ID, or any side effects. The schema requires name and colourCode, but the description does not clarify that these fields will be overwritten.

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 a single, direct sentence. It is concise and front-loaded with the action. The parenthetical '(Tags: Labels)' adds minor clutter but does not harm clarity. Every word is necessary.

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?

For a mutation tool with no output schema and moderate parameter count, the description is insufficient. It lacks details about prerequisites (e.g., label must exist), return value, and error conditions. Sibling tools like label-byPublicId suggest a read-then-update pattern, but this is not hinted.

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 50% (requestBody has a description, labelPublicId does not). The description adds no parameter information beyond what the schema provides. Since coverage is not low (<50%), the description does not need to compensate heavily, but it does not add value either.

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 verb 'Updates' and the resource 'label', identifying the specific identifier 'public ID'. This distinguishes it from sibling tools like label-create, label-delete, and label-byPublicId, which have different actions.

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 (e.g., label-byPublicId to verify existence first, or label-create if the label doesn't exist). There is no mention of prerequisites or contexts.

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