acp_bulk_restart_sessions

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

No annotations are provided, so the description carries the full burden. It reveals the session limit (max 3) and the confirm requirement, which signals destructiveness. However, it does not disclose side effects, partial failure behavior, or prerequisites (e.g., sessions must be stopped).

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?

Two concise sentences, front-loaded with the core action. Every word serves a purpose. No 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?

For a bulk action with no output schema, the description lacks details on success/failure behavior, partial execution, and required session state. It meets minimal needs but leaves gaps that could mislead an agent.

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 documents each parameter. The description adds value only by restating the confirm requirement and implying the sessions limit, but does not clarify the 'dry_run' or 'project' parameters beyond the schema.

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 ('Restart'), the resource ('multiple stopped sessions'), and a constraint ('max 3'). This distinguishes it from singular restart or bulk stop operations.

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 implies use for multiple stopped sessions by specifying 'multiple' and a limit of 3, but does not explicitly contrast with singular restart (acp_restart_session) or mention that sessions must be stopped. The mention of confirm=true hints at destructiveness but no explicit when-not-to-use.

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