postpone_task

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

Describes the core behavior (moves due date by one day) and that it returns updated task details. However, no mention of edge cases like tasks without a due date, recurring tasks, or side effects. Without annotations, more detail would be helpful.

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 with a clear one-line purpose, followed by Args and Returns sections. No unnecessary words or 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?

For a tool with 4 optional parameters and no schema descriptions, the description provides basic parameter explanations and return info. Missing context on behavior when multiple parameters are set, error handling, or default assumptions.

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 coverage is 0%, so description carries the burden. The Args section provides brief descriptions for each parameter (e.g., 'Task name to search for'), adding meaning over the schema names. But does not explain interaction or which parameter takes precedence when multiple are provided.

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 ('postpone a task') and the effect ('moves due date by one day'). It distinguishes from siblings like set_task_due_date which sets a specific date, and move_task which changes list.

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 on when to use this tool versus alternatives such as set_task_due_date for postponing by more than one day. No context about prerequisites or exclusions.

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