gh_edit_label

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

The description adds valuable context beyond the annotations by explaining that the tool is disabled unless MCP_GH_ALLOW_WRITE_COMMANDS=true and that a human approval may be required by default. This discloses operational behavior that the destructiveHint and readOnlyHint annotations do not cover.

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 two sentences, front-loaded with the primary purpose, and the second sentence provides a crucial operational constraint. Every sentence 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 mutation tool with 6 parameters and no schema descriptions, the description is incomplete. It mentions the human approval requirement but fails to explain parameter semantics, what 'edit' entails (e.g., partial updates), or how to rename a label. The output schema partly mitigates return-value explanation, but the overall contextual guidance is insufficient.

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%, and the description provides no explanation of the parameters. The meaning of fields like 'name' vs 'new_name', color format, or description content is entirely unspecified, leaving the agent to guess how to correctly invoke the tool.

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 action ('Edit'), the resource ('existing label'), and the scope ('in a repository'). This distinguishes it from sibling tools like gh_create_label and gh_list_labels, making the purpose unambiguous.

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 context is implied by 'existing label' and the presence of sibling tools like gh_create_label, but there is no explicit guidance on when to choose this tool versus alternatives. The environment flag constraint (MCP_GH_ALLOW_WRITE_COMMANDS) is a usage prerequisite but not comparative guidance.

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