github_issues_delete_label

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

The description does not disclose any behavioral traits beyond the delete operation. No annotations are provided, so the agent gains no insight into side effects (e.g., removal from all issues), auth requirements, or rate limits.

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?

Extremely concise at 3 words, but lacks sufficient information. It is front-loaded but not helpful. Every sentence should earn its place; this one barely does.

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, the description is incomplete. It does not specify success behavior, confirm it deletes an issue label (vs. other label types), or mention that owner, repo, and name are required (though schema covers). No output schema exists, so more context is needed.

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 100% with descriptions for each parameter ('owner', 'repo', 'name'). The description adds no additional meaning or context beyond what the schema already provides. It meets the baseline for high coverage.

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 states 'Delete a label', which indicates the action but is vague about the resource (e.g., issue label). From sibling tools like github_issues_create_label, it is likely an issue label, but the description alone does not specify. This is minimal but functional.

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?

No guidance is provided on when to use this tool versus alternatives like removing a label from an issue (github_issues_remove_label) or updating a label. The description does not differentiate from sibling tools.

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