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

The annotations only say mutating (readOnlyHint=false), idempotent and non-destructive; the description adds real behavioral context: identity, assignments and history are preserved, the change is reversible, and there are no ticket lifecycle, provider or permission side effects. That is exactly the extra detail annotations cannot convey.

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?

Three short sentences, front-loaded with the core action and scope, then the undo path, then the negative side-effect claims. No padding or redundancy.

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 no-output-schema mutation tool this covers the essentials an agent needs: what changes, what is preserved, how to reverse it, and what does not happen. The only remaining gap is return-value/confirmation behavior and any ownership/permission prerequisite, which the description asserts are unchanged but does not spell out.

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?

The single label_id parameter has 0% schema description coverage; the description only implies the label must be 'owned' and gives no format, lookup or validation guidance beyond the schema's uuid format. With one param and schema doing most of the work, this is minimally adequate.

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 (archive/hide) and resource (label) with precise scope: 'Hide an owned label from default suggestions without deleting its identity, assignments or history.' This clearly separates it from ticket_label_update, ticket_label_list, ticket_label_upsert and from ticket_archive, which operates on tickets rather than labels.

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?

It names the inverse operation and how to undo it ('Restore it with ticket_label_update archived=false'), routing the agent correctly for the reverse case. It does not, however, state prerequisites or when an agent should prefer ticket_label_update to set archived=true instead of this dedicated tool.

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