stop_watch

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

Annotations declare destructiveHint=true but do not say which path is destructive. The description supplies exactly that missing context: the default behavior is a reversible pause and destruction only occurs with delete=True. It still omits whether a paused watch can be resumed, so it is not a full 5.

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?

A single compact sentence with the destructive branch parenthetically front-loaded after the default action. Efficient, though the extreme brevity leaves room that could have been spent on watch_id or pause-resume semantics.

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 the tool is simple at two parameters. Still, for a mutation tool with 0% schema coverage the description should at minimum clarify what watch_id refers to and whether pausing is reversible; those gaps remain.

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. It explains the delete flag's effect (suppression) clearly, but says nothing about watch_id beyond it being required, leaving the key identifying parameter unexplained in both schema and description.

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?

States a specific verb (pause/delete) on a specific resource (une surveillance), and distinguishes the two modes via delete=True. It does not, however, differentiate itself from siblings such as list_watches or run_watches_now, which an agent might confuse when deciding which watch tool to call.

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 parenthetical 'ou supprime avec delete=True' gives the condition that switches from pause to delete, which is implicit usage guidance. There is no statement of when this tool should be preferred over siblings, nor prerequisites (e.g. watch must exist or belong to the caller).

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