delete_block

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 clarifies that deletion is an archive (soft delete) rather than permanent removal, and states the return value is the deleted block object. However, it doesn't mention permissions required, whether the operation is reversible, or side effects on child blocks.

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 concise and front-loaded with the core action. The Args and Returns sections are structured but slightly redundant given the input schema exists, though it remains clear and efficient.

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 the tool complexity (simple delete), lack of annotations, and presence of an output schema, the description is minimally adequate. It states the action and return value but omits important behavioral context like permissions, reversibility, and effects on child blocks, which would be helpful for safe invocation.

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 0%, so the description must compensate. It documents the single required parameter 'block_id' and its type (string), which is adequate for a one-parameter tool. The description adds the meaning of the parameter beyond the schema's bare property name.

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 (delete/archive) and resource (block), and the parenthetical clarifies it's an archive operation rather than permanent deletion. However, it doesn't explicitly differentiate itself from sibling tools like update_block or move_page beyond the implied mutation.

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 on when to use this tool versus alternatives. There's no mention of prerequisites, whether the block must be empty, or what happens to child blocks. The agent must infer usage from the name alone.

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