update_task

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

No annotations provided, but description clearly labels as WRITE with side effect (modifies in task app). Explains partial update behavior. Lacks permissions/error info but is otherwise strong.

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 sentences: purpose, side effect, prerequisite + sibling reference. No wasted words. Front-loaded with key action.

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?

Covers purpose, usage, parameters, return, and alternatives. No output schema but description mentions return. Sufficient for a medium-complexity update tool.

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%. Description reinforces that omitted fields stay unchanged, and gives sourcing guidance for IDs – adds meaning beyond schema.

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?

Starts with 'WRITE. Patches an existing item (partial update)' – specific verb and resource. Distinguishes from create_task. Side effect clearly stated.

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 required IDs and where to obtain them (find/list_projects). Provides alternative: 'To create a new item instead, use create_task.'

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