pause_watering

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

Adds behavioral context: zone is paused for specified duration, auto-resumes. No contradiction with annotations (readOnlyHint=false). Could detail error conditions or multiple zone behavior, but adequate.

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?

Very concise: three short sentences for purpose, usage, and parameters. No wasted words, front-loaded with core action.

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?

Covers purpose, usage, and parameters. Output schema present so return values not needed. Could mention edge cases like zone not running, but complete enough for simple tool.

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?

With 0% schema coverage, description fully explains both parameters: device_id is controller UUID, seconds is duration (1-3600). Adds meaning beyond schema.

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?

Description clearly states verb (pause) and resource (currently-running zone), and distinguishes from siblings like stop_watering and resume_watering by specifying automatic resume after seconds.

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 mentions when to use resume_watering for early continuation and implies that pause auto-resumes. Could also mention stop_watering as alternative for permanent stop, but guidance is clear.

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