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

Goes beyond the annotations (readOnly=false, idempotent=true, destructive=false) by disclosing that explicit null clears optional metadata, that identity and assigned ticket strings/history are untouched, and that archiving only hides the suggestion without removing assignments. That last point is exactly the kind of non-obvious behavior an agent needs and is not in any structured field.

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?

Four tight sentences that are front-loaded with the editable surface, then prerequisites, then the null/archive semantics. No filler, though the archiving note sits slightly apart from the rest.

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?

No output schema, and the description covers the mutation's scope, preconditions, and the two subtle behaviors (null-clearing, archive-without-unassign). Adequate for a single-resource partial update; only the absence of explicit sibling routing keeps it off a 5.

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 0%, so the description carries the burden and it does: it maps color, description, group, and archived state to the mutation parameters and adds the null-clearing semantics the schema cannot express. It does not mention label_id's UUID nature or the color hex pattern, but those live in the schema.

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?

Names a specific verb (edit) and clearly enumerates the editable surface: color, description, group, archived state of an owned label. It does not name the closest sibling (ticket_label_upsert) to distinguish create-or-update from targeted edit, so it stops short of the 5.

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 precondition 'Supply at least one metadata field' is stated, which is useful gating. But it never says when to prefer this over ticket_label_upsert or ticket_label_archive, leaving the agent to infer that this is the partial-edit variant.

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