github_add_labels

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

No annotations are provided, and the description only mentions the basic action. It does not disclose whether labels are appended or overwritten, whether label names must pre-exist, permission requirements, or any side effects. This is a significant transparency gap for a mutation tool.

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 brief and efficient, with a single-sentence purpose followed by a clearly structured args list. No unnecessary text, though the args list partially duplicates schema 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 add-labels tool with an output schema present, the description covers purpose and parameters adequately. However, the lack of usage guidance and behavioral details (which would be especially important with no annotations) leaves the description incomplete for fully informed invocation.

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 Args section provides one-line definitions for all five parameters (owner, repo, issue_number, labels, session_name), adding meaning beyond the bare schema titles. While concise, the descriptions are clear and cover all required fields, compensating for the schema's 0% description 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 clearly states 'Add labels to an issue or pull request' with a specific verb and resource, uniquely distinguishing it from sibling tools like update_issue or create_pr_comment.

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 intended use is implied by the name and description, but there is no explicit guidance on when to choose this tool over alternatives, nor any exclusion criteria. It presents the action without context on relationships to other label-related operations.

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