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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true, idempotentHint=false), and the description adds meaningful defaults not in annotations: private-by-default, auto_init defaulting to true with a README, and the elevated-mode requirement for public repos. Minor gap on failure modes and what happens on name collision.

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?

Dense, front-loaded sentences with no filler; the private default and the mode prerequisite come early. The final sentence about later commits on main in default mode is loosely worded and adds less value than the space it takes.

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 an 8-parameter mutation with no output schema and near-zero schema descriptions, the description covers defaults and the public-mode prerequisite but leaves several parameters and the return/result shape unaddressed. Adequate but not complete for this complexity.

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 only 13%, so the description has to carry the load, and it does explain private, auto_init, and gitignore_template naming along with the owner scope. However, homepage, description, license_template, and name format/constraints get no treatment in either place.

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 (create a repository) plus its scope (user account or an installed organisation), which cleanly separates it from read/management siblings such as gh_repo, gh_repos, and gh_repo_settings. An agent can identify the operation without opening the schema.

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?

Provides real selection context: public creation requires the 'change anything' mode, and the target must be an account/organisation where the app is installed. It does not explicitly name when to prefer a sibling (e.g. gh_repo_settings for editing an existing repo), so no full exclusion guidance.

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