Merge fix PR

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

The description adds that it marks the report as fixed, which is not in annotations. However, annotations already indicate destructive and idempotent behavior. The description's mention of 'squash-merge' may conflict with the mergeMethod enum allowing other methods, causing minor inconsistency.

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 a single, clear sentence with no unnecessary words. It effectively conveys the essential purpose and action.

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?

No output schema and no description of return value or side effects beyond marking the report fixed. The description does not mention success/failure indicators or what happens to the report status. Given the destructive nature, more detail would be helpful.

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%, and the description does not add new meaning to the parameters. The mention of 'PR' may confuse as the fixId is a UUID. The description says 'squash-merge' but schema allows multiple methods, so additional clarification would be beneficial.

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 clearly states the action ('squash-merge') and the resource ('fix attempt PR') and the side effect ('mark the linked report fixed'). It distinguishes this tool from siblings like fix_suggest and submit_fix_result by specifying the merge and status update.

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?

No explicit guidance on when to use this tool versus alternatives. The description implies usage when a fix attempt is ready to be merged and the report should be fixed, but no when-not-to-use or alternative names are provided.

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