task_update

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

With no annotations, the description must convey behavior. It implies mutation but does not disclose idempotency, error handling, or permission requirements. The verification hint suggests asynchronous behavior but lacks clarity.

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?

Two sentences, front-loaded with purpose, and no extraneous words. The second sentence adds a critical instruction without redundancy.

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 complexity (10 optional parameters, no output schema), the description is severely incomplete. It fails to specify required parameters, return format, error conditions, or the effect of combining field updates and status transitions.

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?

The input schema has 10 parameters with 0% description coverage, and the tool description provides no explanation of any parameter's meaning, usage, or constraints, leaving the agent without essential context.

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 task fields or transition task status,' which is a specific verb+resource combination. It effectively distinguishes from sibling tools like task_create, task_delete, task_get, task_list, and task_wait.

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 advises to 'Check the verification payload to confirm the requested changes were applied,' providing a useful post-invocation step. However, it lacks explicit guidance on when to use this tool versus alternatives or any prerequisites (e.g., task existence).

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