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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the bar is lower. The description adds real value by disclosing that cancellation affects only further processing (already-produced output presumably persists) and by imposing a confirm-first requirement. It does not say whether cancellation is reversible or what partial results remain, so a 4 rather than 5.

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, each earning its place: the usage gate first, the behavioral effect second, the safety precondition last. No repetition of the title or schema content.

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?

With full schema coverage, rich annotations, and an existing output schema, the description covers the essentials an agent needs to call it correctly. The only remaining gap is post-cancellation state (what happens to partially processed items), a minor omission.

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 100% and batch_id carries a strong 'never guess an ID' instruction plus sourcing from list_batches/submit_batch; batch_type has an enum with per-value docs. The description adds nothing about parameters, so the schema carries the load and baseline 3 applies.

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 ('Stops further processing of a submitted or running job') and scopes it to the batch state, so an agent can distinguish it from submit_batch and list_batches. It does not explicitly name a sibling or contrast with a delete/undo path, which keeps it out of 5 territory.

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?

'Use this only when the user asks to stop a bulk job' gives an explicit usage condition and effectively excludes proactive/casual use. It adds a confirmation precondition ('Confirm first'). It stops short of naming alternatives such as get_batch_status for checking progress first, so not a 5.

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