Delete Buildin block

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

Declares 'permanent removal' which is critical behavioral info, but lacks details on error handling, idempotency, or required permissions. Given no annotations, more transparency would be beneficial.

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?

Two short sentences, no fluff. Action and key differentiator presented upfront. Optimal length for a simple tool.

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?

Adequately describes the core action and key distinction from archiving. Missing mention of error scenarios or idempotency, but given simplicity (one param, no output schema), it is largely sufficient.

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 single parameter block_id is fully documented in the schema (100% coverage). The description only restates it as 'Buildin object ID (UUID-like)', adding no extra meaning beyond the schema.

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?

Clearly states 'hard-delete a block by ID' and explicitly distinguishes from archiving a page, making its purpose unambiguous relative to the sibling tool buildin_archive_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?

Provides explicit guidance on when not to use it (not the same as archiving), but does not mention any prerequisites or alternative deletion tools. Still helpful for differentiating from the archive sibling.

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