doc_delete_blocks

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It clearly indicates a destructive operation (delete) and scopes it to child blocks of a parent, which is useful. However, it does not disclose whether the deletion is permanent, cascades to deeper nesting, or requires specific permissions, which is a gap for a destructive tool.

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 the verb first, followed by the resource and scope. It contains no fluff or redundancy, making it concise and easy to parse.

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 is relatively simple with four required parameters and no output schema. The description covers the purpose and scope but omits details such as return values, reversibility, or likelihood of irreversible changes. Given the lack of annotations, a bit more context would improve completeness, but the description is adequate for basic understanding.

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 coverage is 100%, with all four parameters described (e.g., start_index inclusive 0-based, end_index exclusive). The description's '按位置区间' (by position range) adds no additional semantic value beyond what the schema already provides, so the baseline of 3 is appropriate.

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 the verb '删除' (delete), the resource '飞书文档' (Feishu document), and the specific target '指定父块下的子块' (child blocks under a specified parent block). It also specifies the method '按位置区间' (by position range), which distinguishes it from sibling tools like doc_update_block or doc_create_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?

The description provides clear context on when to use the tool: to delete child blocks under a parent block by position range. It does not explicitly mention alternatives or exclusions, but the purpose is unambiguous enough for an agent to infer the appropriate situation.

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