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

Beyond the annotations (idempotentHint=true, destructiveHint=false, openWorldHint=false), the description discloses non-obvious semantics: canonical aliases keep the first display name/identity, metadata updates are non-assigning, and no provider label writes occur. That is real behavioral context an agent cannot get from the annotations alone.

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 front-load the create/restore action, then layer scope constraints. Each sentence carries distinct information, though 'retain the first display name and identity' is slightly opaque for the space it takes.

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, the description covers the safety/identity behavior well, but it stops short of documenting the three optional metadata parameters or the return shape, leaving gaps an agent would need to fill by guessing.

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% across 4 parameters, so the description carries the full burden. It clarifies that 'name' is normalized and vaguely references 'metadata updates', but color, group_key, and description are never explained, leaving more than half the parameters undocumented anywhere.

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 specific verb pair (create/restore) and resource (owner-private ticket label) and clarifies the normalized-name keying. It implicitly differentiates from ticket_label_update and ticket_label_archive, but never names them, so the sibling routing is left to inference.

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 upsert semantics ('create or restore') imply when to use it, and 'do not assign it to tickets' scopes the operation. However, it never says when to prefer ticket_label_update or ticket_label_archive, so no explicit alternative routing is given.

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