Update tasks

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

With no annotations provided, the description must disclose behavioral traits. It implies mutation but does not clarify consequences like irreversibility, permission requirements, or effects on related data. Terms like 'soft-delete' are not explained.

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 sentence, front-loaded with the primary action, and contains no filler. It is appropriately concise for the tool's purpose.

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 has 10 parameters including nested objects and no output schema, the description is too brief to fully inform an agent. It does not explain parameter interactions, return value, or edge cases like setting both archived and deleted.

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 50% parameter descriptions, which is moderate. The description adds context for some parameters (columnId, completed, archived, deleted) by linking them to actions but does not cover all parameters like deadline or stickers. The schema descriptions cover the rest adequately.

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 a task' and lists specific actions (edit, move, complete, archive, soft-delete), making the primary purpose evident. However, it does not mention other available updates like setting description, assigned, or stickers, which slightly reduces completeness.

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 explicit guidance on when to use this tool versus alternatives like yougile_tasks_create or yougile_tasks_get. The description only states what it does, not the context or prerequisites for using it.

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