Add Note to Task

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

Annotations indicate a non-read-only, non-destructive, open-ended operation. The description adds context by specifying the note is attached to the 'currently running task' and for 'future reference or documentation'. It does not outline side effects or error conditions, but the information provided is sufficient for a simple creation tool.

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?

The description is a single, direct sentence that immediately conveys the tool's purpose. It is front-loaded and contains no unnecessary words or 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?

Given the tool's simplicity (2 parameters, 1 required), an output schema present, and annotations covering safety, the description provides all necessary context. It clearly states the use case and what the tool accomplishes without omitted details.

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?

Both parameters ('text' and 'dateTime') are fully described in the input schema with clear descriptions. The tool description adds no additional parameter-level meaning beyond what the schema already provides, resulting in a baseline score for high coverage.

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 explicitly states the verb 'add', the resource 'a text note or comment', and scope 'to the currently running task'. It clearly distinguishes from sibling tools like task_add_expense or task_add_pause.

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?

The description provides clear context for when to use ('when the user wants to add a text note or comment to the currently running task'). However, it does not mention when not to use this tool or suggest alternatives for modifying existing notes.

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