github_close_issue

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

Annotations are absent, and the description only restates the action without disclosing side effects, permissions, or reversibility; implies mutation but lacks behavioral detail.

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?

Extremely concise, front-loads the purpose, and the arg list is compact without redundant fluff.

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 mutation tool, the description is minimal; it lacks context on when to use it, prerequisites like authentication, or any behavioral notes, though an output schema exists.

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 description provides brief descriptions for each parameter (e.g., 'Repository owner', 'GitHub session to use'), but they largely mirror the property names and add minimal semantic value beyond the schema, which has zero 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?

Clearly states 'Close an issue' with a specific verb and resource, distinguishing it from sibling tools like github_close_pr and github_update_issue.

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 on when to use this tool versus alternatives; merely lists parameters without any context on appropriate usage or exclusions.

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