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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the destructive nature is known. The description adds valuable behavioral context beyond the annotations: the confirm-gated execution model, the preview behavior when confirm is false, concurrent execution, and per-entry ok/error reporting. It does not contradict the annotations.

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 sentences, each earning its place: the first states scope and limit, the second explains the confirm gate, the third explains concurrency and error isolation. The most important operational detail (confirm) is front-loaded, and the sibling comparison is placed at the end where it adds differentiation without distracting.

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 the core usage, safety gate, concurrency behavior, and error handling. The output schema exists, so return values need not be described. The only minor gap is that it doesn't mention the contextRunId parameter or Strict context requirements, but the schema covers that parameter fully, so the description is complete enough for an agent to call the tool correctly.

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%, so the schema already documents all three parameters. The description adds context for confirm (preview vs execute) and pageIds (workspace items or database rows), but these are also partially covered in the schema. The description does not add significant new meaning beyond the schema, so a baseline 3 is appropriate.

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 ('Delete'), a specific resource ('multiple workspace pages, databases, or database rows'), and a key constraint ('max 100'). It also distinguishes itself from the sibling bulk_update_pages by noting the per-entry error behavior, so an agent can tell them apart.

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 explicitly explains when to use the tool (to delete multiple items in one call) and how to use it safely: confirm: true executes, omitting or false previews. It also names the alternative bulk_update_pages and explains why this tool is preferable for deletions where one bad id should not fail the whole batch.

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