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

The description adds real value beyond the annotations by disclosing the required 'repo' scope and the return shape {removed: boolean}, which the agent cannot get anywhere else since no output schema exists. However, 'Idempotent' merely restates idempotentHint=true from the annotations, and there is no explanation of whether the label must already exist or how a missing label/label-not-found case is reported.

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 short, front-loaded sentences with the action first and supporting facts after; nothing is padded. The only near-waste is the 'Idempotent.' sentence, which duplicates an existing annotation rather than adding new 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?

For a simple four-parameter mutation the description covers the essentials - action, safety implication, auth scope, and return value without an output schema. The remaining gap is parameter meaning: with zero schema coverage, the agent still has to guess the semantics of 'label' and 'number' before it can call the tool correctly.

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 four required parameters, so the description carries the full burden and provides none of it. It never clarifies that 'number' is the issue number, whether 'label' is a name or an ID, or what format 'owner'/'repo' take - all of which the schema leaves bare.

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 and resource: 'Detach a label from an issue'. This is clearly distinct from the inverse sibling merjax_label_issue, though it never names that sibling or any other alternative explicitly, so the differentiation is implicit rather than stated.

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?

Usage is only implied by the verb - an agent can infer 'use this to remove a label', but there is no statement of when to use it versus the inverse tool, no prerequisites, and no exclusions. A one-clause pointer to merjax_label_issue for the opposite operation would have lifted this.

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