Submit Batch Review

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

The description adds behavioral context by noting that Bitbucket API does not support pending/draft comments in batch and that each comment is posted immediately. This goes beyond the annotations, which lack any behavioral hints.

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 concise and well-structured, with a clear purpose statement, a behavioral note, and a neatly formatted parameter list. Every sentence adds value without redundancy.

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?

The description covers all parameters, returns a summary, and includes a behavioral note. With an output schema present, it does not need to detail return values, but it still provides a concise overview, making the tool fully understandable.

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?

With 0% schema coverage, the description fully explains the parameters: comments structure (content, inline), review_action enum values, and optional fields. This adds essential meaning that the schema alone does not 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 clearly states the tool's purpose: submitting a batch review on a pull request with multiple comments and optional approval/request changes. This differentiates it from sibling tools like add_pull_request_comment (single comment) or approve_pull_request (only approval).

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 implies usage for batch operations but does not explicitly state when to use this tool over alternatives like multiple single-comment calls. Guidance is implicit rather than explicit.

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