backlog

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

With no annotations provided, description carries full burden and discloses key traits: append-only nature, automatic timestamping, exact-text matching requirement for deletion, and support for multiple annotations per task.

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?

Five sentences with zero waste: core action front-loaded, followed by conceptual definition, cardinality note, alternative reference, and removal mechanism. Logical flow from what→why→when-not→how-to-undo.

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 simple annotation tool with no output schema: covers persistence model (timestamped, stored), lifecycle constraints, and sibling relationships. Minor gap: doesn't describe return value or error states.

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?

Despite 100% schema coverage (baseline 3), adds semantic constraints beyond schema: specifically guides the 'text' parameter with 'Keep concise' and contrasts it with long-form content alternatives.

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?

Opens with specific verb+resource ('Add a timestamped text note to a task') and clearly distinguishes from siblings by naming task_doc_write for longer content and task_denotate for removal.

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 when to use alternatives ('For longer structured content... use task_doc_write instead') and documents the removal workflow ('use task_denotate with the exact text'), providing clear decision boundaries.

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