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

With no annotations, the description carries the full burden and does well: it discloses the branch naming scheme (emdly/…), that files are committed with full new content, that a PR is opened for human review, and critically that existing branches are never mutated. It omits auth/permission requirements, failure behavior, and what is returned (PR URL/number).

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?

One dense but well-structured sentence front-loads the purpose, then walks through branch creation, commit, and PR opening, ending with the key constraint. No filler, though the single-sentence form makes it slightly harder to scan than separated clauses would be.

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 mutation tool with no annotations and no output schema, the description covers the lifecycle adequately and flags the non-destructive boundary. It leaves a gap on return value and error/permission handling, which matters because there is no output schema to explain what comes back.

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 100%, so the schema already documents repo, base, title, body, and files. The description restates the 'full new content per file' semantics, which is the one behaviorally important nuance, but adds essentially nothing beyond the schema baseline.

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 (propose) and resource (a change to a GitHub repo as a pull request) and distinguishes itself from siblings like github_create_issue and github_read by describing the full branch-commit-PR flow. An agent can tell exactly what this tool produces.

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 establishes clear context: use this when you want a human-reviewed PR, and it explicitly bounds the operation with 'Never writes to an existing branch.' It does not, however, name an alternative tool or state when NOT to use it (e.g., for direct commits), so it stops short of the top score.

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