Freelo Update Task Description

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

The description discloses that the previous description is replaced completely, which is important behavioral context beyond what the annotations state. It also notes markdown support. This adds useful transparency without contradicting the idempotentHint.

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 concise sentences with no filler. The core action is front-loaded and the replacement behavior is stated directly, making the definition easy to parse.

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?

For a simple two-parameter update with an output schema and supporting annotations, the description covers the essential behavior: scope, format support, and replacement semantics. Nothing critical is missing.

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 100%, so the schema already documents both parameters well. The description adds supporting context about markdown and full replacement, but does not need to do significant compensating work.

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?

States a specific verb and resource: updates only the description of a task. The word 'only' differentiates it from broad task update tools like freelo_edit_task, and the scope is immediately clear.

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 clearly indicates this is for description-only updates, which tells an agent when to prefer it over freelo_edit_task. It does not explicitly name alternatives or exclusion conditions, but the scope language is strong enough to guide selection.

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