delete_doc_blocks

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

No annotations are provided, so the description carries the full burden of disclosure. It states the action is destructive, but does not mention irreversibility, impact on child blocks, permissions required, or what happens to associated content. This is a minimal description that adds little beyond the tool name.

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 concise sentence that is front-loaded and conveys the core action without any wasted words. It fully fits within the acceptable scope for a simple delete operation.

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's complexity (destructive operation with 3 required params), the description lacks important context: whether deletion is permanent, whether it recursively deletes sub-blocks, and what the expected outcome is. No output schema exists, so the description should provide more behavioral context but does not.

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 has 100% description coverage for all three parameters (team_id, doc_id, block_ids). The description does not add additional parameter semantics, but the schema already fully documents each parameter, so the baseline of 3 applies.

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 content blocks from a ClickUp Doc' uses a specific verb ('Delete') and resource ('content blocks'), and clarifies the container ('ClickUp Doc'). It clearly distinguishes itself from sibling tools like delete_doc or delete_doc_page by targeting blocks.

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 is provided regarding when to use this tool versus alternatives. There is no mention of when to choose delete_doc_blocks over delete_doc or delete_doc_page, nor any exclusions or prerequisites.

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