delete_time_block

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

With no annotations present, the description carries the full burden and delivers: cascade deletion of attachments, a 14-day recoverability window versus permanent purge afterward, and a distinct blocks:delete scope separate from blocks:write that must be granted deliberately. It also pre-empts an incorrect user-facing claim about irreversibility.

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?

Long but denser than it looks: every sentence is a distinct guardrail (target identification, user confirmation, no batching, reversibility window, scope requirement). The destructive action is front-loaded and no sentence is filler.

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?

For an irreversible-leaning destructive tool with no annotations and no output schema, this covers everything an agent needs: exactly what is destroyed, how to confirm, how to recover, what scope is required, and what to tell the user afterward.

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% and the single parameter already documents that the id comes from list_time_blocks. The description only reinforces cardinality ('Exactly one block is deleted'), adding little beyond the schema. Baseline 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?

States a precise verb and resource ('Permanently delete ONE recorded time block') and immediately scopes the side effect ('along with any files attached to it'). The 'ONE' emphasis cleanly separates it from ranged or bulk operations and from siblings like list_deleted_time_blocks and restore_time_block.

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?

Gives explicit preconditions (must show the user the specific block pulled from list_time_blocks and get an explicit yes), explicit prohibitions (never infer from a vague instruction, never delete a range at once), and names the alternative path (restore_time_block within 14 days). Nothing is left to inference.

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