pause_cleaning

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is covered structurally. The description adds real value by stating the robot holds position rather than resetting, but it omits what happens to the paused job (does it stay paused indefinitely? does it resume via start_cleaning?) — relevant for a state-mutating tool.

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 clauses: the action and its state effect come first, the prerequisite second. No filler, nothing redundant with the 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?

An output schema exists, so return values need no explanation, and this is a simple single-parameter tool. The remaining gap is the resumption path after pausing, which an agent may need to plan a sequence.

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 0%, so the description must compensate for the single `duid` parameter. It does add the key missing information — where to obtain the value (list_devices) — but says nothing about the expected format or validity, leaving the identifier's shape undocumented.

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?

Specific verb+resource ("Pause the current cleaning") with an added state consequence ("the vacuum stays where it is") that implicitly distinguishes it from return_to_dock and start_cleaning. It does not explicitly name those siblings, so an agent must infer the contrast rather than being routed.

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 precondition for the required argument is given explicitly ("Get `duid` from list_devices"), which is genuinely useful routing. However, there is no guidance on when to pause versus returning to dock or letting a run finish, and no mention of how cleaning is resumed afterward.

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