backlog

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

No annotations provided, so description carries full burden. Effectively discloses critical behavioral traits: irreversibility ('cannot be undone'), data destruction ('task data is erased'), and state requirement (must be pre-deleted). Lacks only secondary details like error conditions or permissions, but covers essential safety-critical 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?

Three efficient statements with zero waste: opens with permanence warning, follows with prerequisite instruction, closes with alternative suggestion. Every word earns its place; front-loaded with critical safety information.

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?

Complete for a single-parameter destructive operation. Covers purpose, prerequisites, irreversible consequences, and sibling alternatives. No output schema exists, but none is needed as the action is terminal state-change; description adequately covers the operation's behavior.

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 description coverage is 100%, with the id parameter fully documented in the schema ('Task ID number... must be in deleted status'). Description focuses on tool behavior rather than parameter semantics, relying on schema for parameter details — appropriate baseline for high-coverage schemas.

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?

Excellent specificity with 'Permanently and irreversibly remove a deleted task from the database' — clearly identifies the verb (permanently remove), resource (deleted task), and scope. Explicitly distinguishes from siblings by referencing task_delete as a prerequisite and task_archive as an alternative.

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?

Outstanding explicit guidance: states prerequisite ('task must already have status deleted'), provides ordered workflow ('use task_delete first'), and names specific alternative tool ('Use task_archive for bulk cleanup'). Covers both when-to-use and when-not-to-use.

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