gh_create_repo

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the write behavior is known. The description adds valuable context beyond annotations by explaining that the tool is disabled unless MCP_GH_ALLOW_WRITE_COMMANDS=true and that human approval is requested by default. No contradiction with 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?

The description is concise and front-loaded with the core action 'Create a new repository.' The two additional sentences earn their place by conveying critical operational requirements without unnecessary detail.

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 creation tool, the description adequately covers the action and operational gating/approval. The output schema exists, so return values need no explanation. The main gap is missing parameter semantics, but the schema and self-evident field names make the tool usable enough.

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 0%, and the description provides no parameter-level guidance. The property names and defaults in the schema give some clues, but the meaning of parameters like auto_init is not explained, so the description does not 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 opens with 'Create a new repository', a specific verb and resource that clearly states the tool's purpose. This distinguishes it from sibling create tools like gh_create_issue, gh_create_pr, and gh_create_release.

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 does not explicitly discuss when to use this tool versus alternatives; usage is implied from the name and the 'create a new repository' statement. However, it does provide important usage context about the required environment variable and human approval flow, which helps the agent understand operational constraints.

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