Extend Watchdog

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

Annotations indicate readOnlyHint=false, and the description confirms mutation by stating it extends the timer and pushes the deadline. Adds behavioral detail beyond annotations (e.g., prevents reclaim, aborts recipes). No contradictions.

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?

Three short paragraphs, no wasted words. Front-loaded with core purpose. Each sentence adds essential information. Perfectly structured for quick 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 tool's simplicity (3 params, clear purpose, output schema exists), the description covers all needed context: what it does, when to use it, and how to specify the target. No missing information for a typical use case.

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%, so baseline is 3. The description adds value by clarifying the relationship between job_id and task_id (provide either), and the automatic task finding when job_id is given. This improves understanding beyond the schema alone.

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?

Clearly states it extends the watchdog timer for a Beaker task. Uses specific verb+resource ('extend watchdog timer') and explains the effect (prevents reclaim, pushes deadline). No sibling tool does this, so differentiation is inherent.

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?

Explicitly tells when to use: to extend a reservation and prevent system reclaim. Provides context about Beaker's watchdog behavior. Does not explicitly list alternatives or when not to use, but given the tool is unique among siblings, this is sufficient.

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