delete_label

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

The description discloses key behavioral traits: irreversibility ('Irreversible') and the fact that it 'Signs and broadcasts an on-chain transaction'. This adds value beyond the absence of annotations, which carry no information. However, it does not mention potential side effects like gas costs or confirmation times.

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 extremely concise: a single sentence plus a 'See also' line. It immediately states the purpose, mentions irreversibility, and lists required parameters. Every word earns its place with no redundancy or filler.

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 delete tool with three parameters and no output schema, the description covers essential aspects: purpose, usage context, behavioral traits, and related tools. It is complete enough for an agent to understand when and how to use 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?

The input schema has 100% description coverage for all three parameters. The description adds limited extra meaning: it repeats the required parameters (already clear from schema) and hints that label_id comes from list_labels. This is marginal improvement, so baseline 3 is appropriate.

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 states the tool's purpose: 'permanently remove a label from a repository'. It uses a specific verb ('remove') and resource ('label from a repository'), and distinguishes from sibling tools by referencing 'list_labels' and 'create_label'.

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 description provides clear when-to-use guidance ('Use this when you need to permanently remove a label') and mentions required parameters. It references alternatives ('See also: list_labels, create_label'), but does not explicitly state when not to use this tool, such as when an update is needed instead of deletion.

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