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

Annotations already declare this as destructive and open-world, but the description adds no details about what gets overwritten, whether local changes are affected, or what permissions are needed. It only restates the pull action and target branch.

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?

A single short sentence with no waste and the action is front-loaded. It is appropriately sized for a simple pull operation.

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 destructive mutation with no output schema, the description is too thin: it does not explain prerequisites, effects on local state, or what success looks like. Annotations cover safety flags but the description should carry more operational context.

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 100%, so the single project_id parameter is already documented in the schema. The description does not mention project_id or session fallback, but with full schema coverage the baseline is 3.

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: 'Pull from the linked GitHub base branch.' It is clear what operation is performed, though it does not explicitly distinguish this from the sibling tool github_sync.

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?

It gives no guidance on when to use this tool, when not to use it, or how it differs from alternatives such as github_sync or github_status. The only implied prerequisite is that a repository is already linked.

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