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

Annotations already disclose that this is a non-read-only, non-idempotent, non-destructive mutation. The description adds useful context about the baseBranch default and SERVICE_UNAVAILABLE failure behavior, but it does not warn about duplicate PR creation or explain permission/ledger constraints in detail.

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 tightly packed sentences with the core action first, followed by required inputs, default behavior, and error behavior. There is no redundant restatement of the tool name or title.

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 seven-parameter mutation tool with low schema description coverage, the description gives enough to call it correctly: required fields, changes structure, baseBranch default, and error behavior. The output schema handles return values, though some parameter nuances remain delegated to the schema.

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 29%, so the description must compensate. It names the required parameters, describes the changes array shape, and states the baseBranch default, but it does not explain all parameter semantics, especially ledger and fastForward, beyond what their schema descriptions already provide.

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 states a specific verb and resource: propose file changes as a pull request. It is clearly distinguishable from sibling operations like mergePullRequest and rejectPullRequest.

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 purpose implies when to use it, but the description does not explicitly contrast it with mergePullRequest, rejectPullRequest, or other file-management tools. No exclusions or prerequisite workflow guidance are provided.

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