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

Annotations already declare readOnly=false, idempotent=false and openWorld=true, so the description isn't required to restate non-safety. It does add that a real check is executed and the fresh result is returned, but it omits meaningful traits an agent would want: whether a failing result can fire alerts/incidents, whether repeat calls are wasteful, and any rate limiting.

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 tightly written sentences, front-loaded with the action and its scope, with zero filler.

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 simple single-parameter trigger with full schema coverage and clear annotations this is nearly sufficient, but there is no output schema and the description does not characterize the returned 'check result' or disclose the alert/incident side effect of a failing check.

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 100% for the single required 'id' parameter, so the schema already documents it. The description adds no extra meaning about the identifier (e.g., must be an existing, non-deleted monitor), so this lands at the baseline.

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 ('Trigger an immediate check') and resource ('a monitor'), and the parenthetical clarifies it supplements rather than replaces the scheduled cadence. It is clearly distinct from config-mutation siblings like vs_monitors_update_* or vs_monitors_pause, though it never explicitly names a sibling.

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 'in addition to its scheduled cadence' clause implies this is for on-demand verification when you don't want to wait for the next scheduled run. There is no explicit when-not guidance and no pointer to alternatives such as the one-off vs_website_check / vs_dns_check tools.

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