backlog

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

With no annotations provided, the description carries full burden and successfully discloses 'permanently deleted' nature and side effects ('Clears the +doc tag and has_doc field'). Missing only minor details like error behavior when task lacks a document.

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?

Four sentences total with zero waste: purpose (sentence 1), side effects (sentence 2), destructive warning (sentence 3), and alternative tool (sentence 4). Information is front-loaded and dense.

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?

Comprehensive for a single-parameter destructive operation. Covers deletion scope, metadata side effects, irreversibility, and alternatives. No output schema exists, but description adequately explains outcomes without needing return value documentation.

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 the 'id' parameter fully documented as 'Task ID number (e.g. '1') or UUID'. Description does not need to add parameter syntax details, warranting baseline score 3.

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 uses specific verb 'Remove' with clear resource 'markdown document attached to a task', distinguishing it from sibling tool task_delete (which deletes the entire task) by specifying this only removes the attached document.

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?

Explicitly states the alternative tool for different intent: 'To update a document instead of removing it, use task_doc_write', providing clear when-to-use guidance against its direct sibling alternative.

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