github_issues_get_label

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

In the absence of annotations, the description must disclose behavioral traits, but it only states 'Get a label' with no mention of side effects, permissions, rate limits, or return format. It provides no useful behavioral context.

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?

At three words, the description is extremely short but under-specified. It sacrifices clarity for brevity and does not earn its place as a useful description.

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?

With no output schema, no annotations, and minimal parameter info, the description should provide comprehensive context. It fails to explain what the tool returns, its limitations, or how it fits into workflows.

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?

Although schema coverage is 100%, the parameter descriptions are minimal placeholders (e.g., 'owner', 'repo', 'name'). The tool's description adds no meaning beyond these, failing to explain the parameters' roles in the GitHub context.

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 'Get a label' is a tautology that merely restates the tool name without specifying that it retrieves a specific GitHub issue label from a repository. It fails to distinguish this tool from other 'get' tools among hundreds of siblings.

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, its prerequisites, or how it differs from alternative tools like getting an issue or a repository. The description offers no context for appropriate invocation.

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