task_update

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

With no annotations and a description that only names the tool, there is no disclosure of behavioral traits such as whether the operation is destructive, requires permissions, or has side effects. The agent gets no insight into system impact.

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 extremely short (5 words), but this is under-specification rather than conciseness. It fails to front-load any useful information and offers no structure to aid comprehension.

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 complexity of 6 parameters, 1 required, and the existence of an output schema, the description provides zero contextual information. For a mutation tool, this is severely incomplete and burdens the agent with inference.

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 6 parameters with 0% description coverage, yet the description adds no explanation for any parameter. The agent must rely solely on parameter names, which are insufficient for understanding format, constraints, or relationships.

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 merely repeats the tool name 'task_update' with a generic prefix, offering no specific verb or resource explanation. It vaguely suggests updating a task but lacks any detail on what aspects are updated, making it only slightly better than a tautology.

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 like task_create or task_list. The description fails to specify any context or exclusion criteria, leaving the agent without decision-making support.

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