Update a label

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

Annotations are minimal (only title), so description carries the burden. It states 'Update' (mutation implied) and partial update behavior, but no details on success response, side effects, permissions, or error cases. More transparency needed.

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?

Extremely concise with two sentences: first states purpose, second gives usage guideline. No wasted words, front-loaded key information.

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 no output schema, complex nested fields object, and 2 parameters, the description is too sparse. Lacks details on allowed fields, response, errors, or prerequisites for a partial update tool.

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 has 50% coverage: label_id has no description, fields has 'same field set as create_label' which adds meaning. Description adds value for fields but not for label_id. Baseline 3 partially justified.

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 action ('Update') and resource ('a label'), using a specific verb and resource. It differentiates from sibling tools like create_label and delete_label by the verb 'update'.

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?

Provides clear guidance: 'Supply only the fields you want to change in `fields`.' This indicates a partial update pattern, helping the agent use the tool correctly. Does not explicitly state when to use alternatives, but context is inferred.

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