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

The description adds a genuine behavioral fact beyond the annotations: the call can be rejected when balance is empty. But annotations flag destructiveHint=true and openWorldHint=true on what reads like a simple resume, and the description does nothing to explain what is destroyed or what external effect occurs. It also doesn't say whether runs missed while paused fire immediately on resume, which is the key behavioral question for a resume operation.

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 short sentences, zero filler, with the action stated first and the blocking condition immediately after. Nothing is repeated from the title or schema.

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 one-parameter tool with no output schema and decent annotation coverage, the description covers purpose and the main failure mode. What's still missing is the resume semantics (missed-run catch-up, in-flight deliveries) that would explain the destructive hint, but the essentials for calling it correctly are present.

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 100% and the single 'id' parameter is fully documented in the schema, including where to obtain it (create_task or list_tasks). The description adds no parameter meaning beyond that, so the baseline 3 applies.

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 verb phrase 'Start firing again on the schedule' makes clear this re-activates scheduling on a paused task, and the title confirms it. It's specific enough to distinguish from pause_task and delete_task, but 'firing' is jargon and it never names run_task_now as the one-shot alternative, so the boundary with that sibling is inferred rather than stated.

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?

'Refused if your balance is empty — buy deliveries first' gives a concrete precondition and a remediation path, which is real usage guidance. However, there is no statement of when to prefer this over run_task_now (immediate single run) or how it relates to create_task/restore_task, so the routing guidance is only implicit.

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