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

Annotations already declare readOnlyHint=false, openWorldHint=true, and destructiveHint=false, so the safety profile is covered externally. The description adds the '[WRITE]' marker and the confirm gate, which reinforces intent, but says nothing about what the call returns (issue number/URL) or that the issue is visible to others immediately. With annotations carrying the main burden, this is adequate but thin.

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?

Two short sentences, zero filler, with the write marker and confirm requirement front-loaded. Nothing here is wasted or buried.

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 create operation with full schema coverage and clear annotations, the description covers enough to invoke correctly. However, with no output schema, an agent gets no hint of what comes back (issue URL or number), which is commonly needed to chain into github_comment or a follow-up read.

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 100%, with each of the five parameters (including confirm and the owner/name repo format) documented inline. The description adds no syntax, format, or constraint detail beyond the schema, so the baseline of 3 applies.

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?

States a specific verb and resource ('Open a new issue in a GitHub repository') that an agent can immediately distinguish from github_get_issue, github_comment, and github_create_pr. It does not explicitly name a sibling or contrast with one, but the name-plus-description pairing is 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 is only implied by the tool name and the '[WRITE]' tag; there is no statement of when to use this versus github_comment or github_create_pr, and no prerequisite context (e.g., repo must exist, labels must pre-exist). The 'Requires confirm:true' note is the only explicit usage guidance, and that is already restated in the schema.

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