pr_batch

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

With no annotations, the description does carry real behavioral information: sequential ordering, fail-fast with stopOnError, and one result per op. It omits whether earlier successful ops are rolled back on failure, and whether partial results are returned when it stops, which are the key unknowns for a batch mutation tool.

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?

Three short sentences, front-loaded with the core action, then the item shape, then the failure semantics. The '{operation, args}' sentence partially restates the schema but is justified given 0% schema description coverage.

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 two-parameter tool with no annotations and no output schema, the description covers ordering, failure behavior, and return cardinality ('one result per op'). It falls short only on atomicity and on identifying valid operation values, which are material gaps for a batch executor.

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 0%, so the description must compensate, and it does explain the shape of each op ({operation, args}) and what stopOnError controls. However, the critical ambiguity is left open: 'operation' is a bare string with no enum, and the description never says where valid operation names come from (presumably pr_catalog/pr_do).

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 a specific verb and resource: runs several operations in order, i.e. a batch executor. It is clear what the tool does, but it never names or contrasts with the obvious sibling pr_do (single-operation execution), so the agent must infer the relationship.

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?

There is no statement of when to batch versus calling pr_do repeatedly, no prerequisites, and no exclusions. The error-stopping behavior hints at a use case but does not tell the agent when this tool is the right choice.

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