modify_task

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

No annotations are provided, so the description must fully disclose behavioral traits. It does not mention idempotency, error handling, side effects, or whether changes are reversible. The dry_run parameter is not explained in the description, leaving the agent unaware of its effect.

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 concise and well-structured, using an args list with examples. Every sentence adds value, though the dry_run parameter could be mentioned briefly without adding much length.

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 an output schema, so return values need not be explained. However, as a mutation tool, it should disclose behavioral aspects like permissions, reversibility, and dry_run behavior. The description is adequate for basic usage but lacks completeness for safe agent invocation.

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 description coverage is 0%, so the description must compensate. It adds meaning for the 'fields' parameter with examples of field:value pairs and tag modifications. However, 'uuid' is only briefly mentioned as 'Task UUID' and 'dry_run' is completely omitted, providing incomplete 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 clearly states the action: 'Modify fields on an existing task.' The verb 'Modify' and resource 'fields on an existing task' are specific. This distinguishes it from siblings like create_task, delete_task, and bulk_modify, which handle different operations.

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?

No guidance is provided on when to use this tool versus alternatives such as bulk_modify for multiple tasks or annotate_task for specific fields. There is no mention of prerequisites, limitations, or when not to use it.

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