update_label

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

With no annotations, the description carries the full burden of disclosing behavioral traits. It only says 'update,' which is already implied by the tool name, and does not explain side effects, idempotency, permissions, or patch semantics. This is a significant gap for a mutation tool.

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 only three words and under-specifies the tool's behavior and parameters. This is not appropriate conciseness but rather a near-tautology that fails to earn its place beyond restating the name.

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 has a complex patch object, no output schema, and no annotations, the description is extremely incomplete. It provides no information about expected response, how patch is applied, or any constraints on updates.

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 coverage is only 33% (only workspace_id has a description). The description does not add any meaning about the required 'patch' object or 'id' parameter. For a tool with an arbitrary patch object, this lack of parameter guidance is a critical omission.

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 identifies the operation ('Update') and the resource ('an issue label'), which distinguishes it from sibling tools like create_label, delete_label, and update_issue. However, it is a minimal restatement of the tool name with no added context about what aspects of a label can be updated.

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 regarding when to use this tool versus create_label, delete_label, or list_labels. The description does not mention any prerequisites, alternatives, or context for updating an issue label.

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