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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered structurally; the description adds the genuinely useful clarification that targets are untouched, preventing confusion with remove_target. It falls short of saying whether the stopped watch is deleted or merely deactivated, and whether it can be resumed.

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 sentences, zero filler, with the action and scope front-loaded and the identifier sourcing plus the exclusionary note following in priority order. Nothing needs trimming.

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 destructive, idempotent mutation with no output schema, the definition covers what to pass and that targets are unaffected, but omits what actually happens to the watch object (deleted vs. paused), whether reinstatement is possible, and what a successful call returns. These are real gaps for an agent that may need to warn a user before acting.

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 only 33% (only `name` is documented), so the description must compensate and it partly does by naming all three input forms and framing them as alternative identifiers. However, it never says that exactly one of company/name/watch_id is expected, says nothing about watch_id format, and leaves `company` completely unexplained.

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?

"Stops watching a company or a space for the rep" pairs a specific verb with the exact resource and scope, and the parenthetical example ("stop watching Abiomed") removes ambiguity. An agent can distinguish this from watch_company, save_space_watch, and remove_target without opening any schema.

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?

It explicitly tells the agent where to get the identifier ("the watch's name or watch_id from list_watches"), which routes to the correct sibling for discovery. It also implicitly demarcates itself from remove_target via "Targets are not changed," but never states when one would stop a watch versus delete it, nor any prerequisite/permission context.

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