Delete Block

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

With no annotations, the description fully discloses behavioral traits: removes descendants by default, can keep orphans, can prune connectors, and refuses affine:page. This covers side effects and constraints.

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 that front-load the core action. Every word adds value with no fluff.

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 deletion tool without an output schema, the description is complete: it explains what is deleted, side effects, optional behaviors, and a key limitation. No missing context.

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?

The input schema covers all 5 parameters (100% coverage). The description adds meaning beyond the schema by explaining default behaviors (deleteChildren=true, pruneConnectors=false) and the special case for blockId (refuses affine:page).

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 'Delete a block by id' with a specific verb and resource. It distinguishes from sibling tools like delete_doc by noting 'Refuses affine:page — use delete_doc for whole docs.'

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?

Explicitly explains when to use this tool (delete block by id) and when not (use delete_doc for whole docs). It also details options like deleteChildren and pruneConnectors with their effects.

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