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

The description discloses important side effects beyond the annotations: it advances each story's per-branch baseline, accepts stories with prior denied reviews, leaves failed stories unaffected, and returns the post-acceptance triage. This gives the agent a clear model of what changes and what does not.

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 well-structured and front-loaded: main action first, then usage condition, then behavioral side effects, then return behavior. Every sentence adds useful information and there is no filler.

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 mutation tool with annotations and an output schema, the description covers the key behavioral context: what gets accepted, which stories are affected, what happens to baselines, and what the response contains. No essential operational detail is missing.

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%, so the schema already explains each parameter. The description only restates the identifiers ('commitSha/prNumber/buildId') without adding new meaning such as precedence, mutual exclusivity, or default behavior when multiple are supplied.

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: 'Accept ALL changed stories in one build at once.' It also distinguishes itself from the sibling tool review_diff by explicitly calling itself 'the bulk form of review_diff=accept,' so an agent can correctly separate it from per-story review tools.

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 an explicit usage condition: 'use it when you've decided the whole build's changes are intended.' It also names the relevant alternative (review_diff) and implies per-story review for non-bulk decisions, giving clear routing guidance.

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