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

No annotations are provided, so the description carries full burden for behavioral disclosure. It fails to mention that deletion is destructive/permanent, whether child blocks are recursively deleted, or error conditions. Additionally, the description uses plural 'blocks' while the schema only accepts a single block_id, creating ambiguity about batch deletion capability.

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 brief (4 words) and front-loaded, but for a destructive operation with no annotations, this brevity constitutes under-specification rather than efficient communication. Every word earns its place, but critical information is missing.

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?

Given this is a destructive mutation tool with no annotations and no output schema, the description is inadequate. It omits permanence warnings, return value information (success/failure indicators), and the aforementioned plural/singular discrepancy leaves the actual capability ambiguous.

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%, establishing a baseline of 3. The description adds minimal value regarding the block_id parameter itself, though 'from a page' provides ownership context. The plural 'blocks' in the description slightly conflicts with the singular block_id parameter in 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 uses a specific verb ('Delete') and resource ('blocks') and provides context ('from a page'). However, it fails to distinguish from the sibling tool 'append_blocks' or clarify when deletion is preferred over updating.

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?

No guidance provided on when to use this versus alternatives, prerequisites (e.g., permissions), or warnings about permanent deletion. The description stands alone without operational context.

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