update-tasks

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

The description does not add behavioral context beyond what annotations already provide. Annotations indicate destructiveHint=true (modifies state), but the description fails to mention that unchanged fields remain as-is, that multiple tasks can be updated in one call, or any side effects. No contradiction with annotations.

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, clear sentence that is efficiently front-loaded with the action ('Update existing tasks'). It is concise but could include a brief note about partial updates without sacrificing brevity.

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?

The tool has one parameter with 100% schema coverage and an output schema present. However, the description is minimal and does not tie together the update semantics (e.g., that only provided fields are modified). For the complexity of updating tasks, the description could be more informative.

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?

Input schema has 100% coverage with detailed property descriptions. The tool description mentions example categories (content, dates, priorities, assignments) but adds no new semantics beyond the schema. Baseline 3 is appropriate.

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 'Update existing tasks' and lists specific categories of fields (content, dates, priorities, assignments), making the tool's purpose unambiguous. It distinguishes from sibling tools like add-tasks and delete-object.

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 implies usage for modifying existing tasks but provides no explicit guidance on when to use this tool versus alternatives (e.g., add-tasks for creation, delete-object for removal). No context on prerequisites or exclusions is given.

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