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

With only openWorldHint annotated, the description carries the behavioral burden and does so well: it discloses the quota/billing consequence (free for plan holders, otherwise consumes one scan) and that it triggers a full scan. It omits whether the call is async or how to track completion, which would have pushed it higher.

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 tight sentences: the action and its contrast come first, followed by cost implications and the id source. No 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 single-param trigger tool with no output schema, the description covers purpose, timing, and cost side effects. It could note how to observe the resulting scan (e.g. get_scan_status), but nothing essential is missing.

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 monitor_id parameter and the schema already names its sources, so the description's 'takes the monitor id from list_monitors' is largely redundant. Baseline 3 is appropriate.

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+resource ('run a full scan of a monitored site now') and explicitly contrasts with the scheduled path ('instead of waiting for its schedule'), which distinguishes it from the sibling monitors/scan 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?

Gives a clear triggering condition ('e.g. to confirm a fix') and points to list_monitors for the required id, but does not say when to prefer it over siblings like scan_url or how it relates to get_scan_status for follow-up.

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