gh_create_release

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

While annotations indicate destructiveHint=true and readOnly=false, the description adds operational specifics: the tool is disabled unless MCP_GH_ALLOW_WRITE_COMMANDS=true and requires human approval by default. This is valuable context for the agent beyond the annotations.

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 sentences, front-loaded with the core action. The second sentence earns its place by disclosing critical operational constraints. No unnecessary words.

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?

The description covers the action and important operational safeguards, but with 8 parameters and zero schema coverage, it leaves parameter semantics entirely to the agent. The existence of an output schema helps, but the tool's complexity demands more detail for complete guidance.

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 provides no explanation of the 8 parameters (owner, repo, tag_name, body, name, draft, target, prerelease). The agent must rely solely on parameter names, which are self-explanatory only for GitHub experts.

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 uses a specific verb ('Create') and resource ('a new release'), clearly distinguishing it from sibling tools like gh_create_issue or gh_create_repo. It unambiguously states the operation's scope.

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 description provides no guidance on when to use this tool versus alternatives (e.g., gh_create_pr or gh_create_repo), and does not mention prerequisites or exclusions. The usage is implied by the name and purpose, but not explicitly stated.

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