github_add_labels_to_issue

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. However, it only mentions routing infrastructure (JWT, tenant, company scope) without any information about whether the operation is destructive, idempotent, rate-limited, or what happens on failure.

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 short but wastes space on technical routing details that are likely irrelevant for tool selection. Every sentence should add value, and here both sentences are either tautological or extraneous.

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?

Given the lack of annotations and output schema description, the description is completely inadequate. It does not explain how to form the arguments, what labels can be added, or any expected behavior. A mutation tool with zero annotation coverage needs significantly more context.

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 0%, and the description adds no meaning beyond the schema. It simply restates that the 'arguments' parameter is a JSON string, without describing what keys or values are expected. This fails to compensate for the lack of schema descriptions.

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 merely restates the tool name in a technical format ('Github connector operation add_labels_to_issue'), adding no new information about what the tool does. This is essentially a tautology, similar to the 'Process' calibration example. The name itself is clear, but the description fails to articulate the purpose beyond the name.

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_remove_label_from_issue or other GitHub issue operations. The description gives no context about typical use cases or prerequisites.

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