update_todo

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

Discloses key behaviors: updates only the first open match, tags replace unless using add_tags, returns empty string if no match. With no annotations, this is good but could mention error handling or idempotency.

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?

Well-structured with a clear main sentence followed by bulleted parameter explanations. Each sentence adds value, but length could be slightly reduced without losing clarity.

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 main update scenarios, return format, and parameter interactions. Missing edge cases like validation or error handling, but adequate given 7 params and output schema.

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 0%, so description carries full burden. It explains each parameter's purpose, interactions (e.g., exact with query), and behavior (tags replacement vs append). Adds significant value beyond property names.

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 clearly states the verb 'Update' and the resource 'the first matching OPEN to-do', with specific identification methods (todo_id or name query). This distinguishes it from sibling tools like complete_todo or add_tags.

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?

Provides explicit alternative for appending tags ('Use add_tags to append'), and notes precedence of todo_id over query. However, it lacks explicit when-not-to-use scenarios or prerequisites like requiring either todo_id or query.

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