notion_delete_block

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

With no annotations, the description should disclose behavioral traits. It fails to mention whether deletion is permanent, affects child blocks, requires specific permissions, or supports undo. The routing information is generic and irrelevant to behavior.

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 short but includes unnecessary routing details. It could be more concise by focusing on the delete action, though it is not overly verbose.

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 presence of an output schema (unseen) and sibling tools, the description lacks essential context about returns, side effects, and differentiation from related operations. It fails to explain what a block is or confirm irreversibility.

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 schema coverage is 0%. The description only notes that 'arguments' is a JSON string for the connector operation, but does not list expected keys (e.g., block_id) or format. This adds minimal semantic value beyond the schema type.

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 merely restates the tool name as 'Notion connector operation delete_block' without specifying what a block is or the effect of deletion (e.g., permanent, reversible). It does not differentiate from sibling tools like notion_archive_page or notion_trash_page.

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 on when to use this tool versus alternatives such as archive or trash operations. The description lacks any context about prerequisites, conditions, or scenarios for deletion.

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