delete-block-by-id

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only says 'Delete a block by its ID' without mentioning whether deletion is permanent, cascading, requires permissions, or what happens if the block does not exist. This lack of context is a significant gap for a destructive operation.

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 a single, front-loaded sentence with no redundant words or filler. It conveys the essential information efficiently and is appropriately sized for the tool's simplicity.

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 tool has no annotations and no output schema, and the description does not clarify side effects, error behavior, or reversibility. Even though the schema covers the single parameter, the overall lack of contextual detail makes the description incomplete for a delete operation, especially given the destructive nature.

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 already provides a clear description for blockID ('ID of block to delete'), and the description's phrase 'by its ID' adds no extra semantic meaning. Since schema coverage is 100%, a baseline score of 3 is appropriate; the description does not need to compensate.

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 'Delete a block by its ID' uses a specific verb (delete) and resource (block), and explicitly differentiates from sibling tools like delete-block-from-page-area by specifying deletion by ID. It is direct, unambiguous, and clearly names the action and target.

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?

There is no information about when to use this tool versus alternatives such as delete-block-from-page-area, nor any prerequisites, exclusions, or recommended context. The description only states what it does, not when to choose it, leaving the agent without guidance on selection.

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