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

Beyond the annotations, the description discloses a key side effect: pausing also disables associated automations, which is not inferable from the schema or name. It remains consistent with readOnlyHint=false, idempotentHint=true, and destructiveHint=false. It doesn't cover edge cases like already-paused watches, but the idempotency annotation mitigates that.

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, front-loaded with the primary action and side effect, followed by the one relevant alternative. No filler or repeated schema content.

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 single-parameter state-change tool, the description covers the action, the automations side effect, and the resume path. It omits explicit guidance on how to obtain the watchId, but the get/list competitor-watch siblings cover that; annotations handle safety and idempotence.

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 0%, so the description should compensate, but it never explicitly names watchId. However, the single required parameter is self-descriptive ('watchId') and the description's 'a competitor watch' makes clear which identifier is expected, so the gap is minor.

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 ('pauses'), a clear resource ('competitor watch'), and a concrete side effect ('disables its associated automations'). It also names the resume counterpart, so an agent can distinguish it from resume and from related pause tools.

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 description explicitly points to campaignstack_resume_competitor_watch for the reverse operation, giving clear context on when to use the counterpart. It does not explicitly contrast with delete_competitor_watch or other watch variants, but the pause/resume symmetry makes the intended use obvious.

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