gitea_merge_pull_request

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

No annotations provided, so description carries full burden. 'Merge' implies a write operation but description fails to disclose idempotency, error cases (e.g., if already merged), side effects (branch deletion option exists but isn't explained), or return value format.

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?

Single sentence description is appropriately brief, but the '[UNIFIED]' prefix appears to be implementation metadata rather than descriptive content, slightly cluttering the definition.

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 complex mutation tool with 8 parameters, no output schema, and no annotations, the one-sentence description is insufficient. Missing: merge method options, branch deletion behavior, merge commit message customization details, and error scenarios.

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 has 0% description coverage for 8 parameters. Description mentions 'specified merge method' implying the method parameter, but doesn't explain valid values (merge/squash/rebase), nor does it explain title/message (custom commit message?), delete_branch_after_merge, or the required site/owner/repo identifiers.

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 clear verb 'Merge' and resource 'pull request', and hints at the merge method parameter. However, lacks differentiation from sibling tools like gitea_close_pull_request or gitea_update_pull_request. The '[UNIFIED]' prefix appears to be metadata noise.

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 no guidance on when to use this tool versus alternatives (e.g., close vs merge), prerequisites (required approvals, conflict resolution), or error conditions. No mention of required permissions or repository state.

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