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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutation profile is covered. The description adds genuinely useful scope detail beyond that: stopping affects only the monitor and not research history or other members' monitors, which is exactly the kind of blast-radius information an agent wants before a destructive call.

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, action stated first, scope caveat second. No filler, no repetition of the title.

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?

With an output schema present, return values need no explanation, and annotations carry the destructive/read-only profile. The description's remaining need—identifying which monitor id to pass—is the only real omission for this one-parameter 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?

Schema coverage is 0% and the single parameter (taskId, uuid) is never mentioned in the description. "One of your persistent monitors" implies you supply an identifier, but the description gives no hint of format or where to obtain the id (e.g. list_asset_monitors). Self-evident enough not to be a severe gap, but it fails to compensate for the coverage gap.

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 ("Stop") and resource ("one of your persistent monitors"), which is clearly distinct from siblings like create_asset_monitor, list_asset_monitors, and check_asset_monitor. It doesn't explicitly name alternatives, but the action and scope are unambiguous.

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?

Usage is implied by the name and the word "persistent monitors," but the description never says when to use this versus check_asset_monitor or list_asset_monitors, nor what prerequisites (e.g. an active monitor) apply. The exclusion sentence covers consequences, not when-to-use.

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