github_issues_create_label

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

The description implies a write operation ('Create') but provides no detail on side effects, permissions required, or behavior if the label already exists. With no annotations, the description carries the full burden of behavioral disclosure, which it fails to meet.

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 a single short sentence, making it concise but too minimal to be informative. It does not waste words but also does not add value beyond the tool name.

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?

There is no output schema, and the description does not mention return values or success/failure indicators. For a creation tool, the agent would benefit from knowing what the response looks like. Additionally, the tool interacts with a moderately complex API (GitHub issues), yet the description provides no context about the expected input structure for the body.

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?

All three parameters have descriptions in the schema (100% coverage), so the description adds no extra meaning. The 'body' parameter's schema indicates it is a JSON object with additional properties, but no guidance is given on required fields like name, color, etc.

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 'Create a label' clearly states the verb and resource, but it does not specify whether it's an issue label or a repository label. Given sibling tools like 'github_issues_delete_label', it is understood to be about issue labels, but the description lacks specificity to differentiate from other label operations.

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 'github_issues_update_label' or 'github_issues_delete_label'. Prerequisites (e.g., required permissions, label existence) are not mentioned.

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