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

Annotations already flag idempotentHint=true and destructiveHint=false, and the description usefully explains the dedupe behavior concretely: an existing site on the same domain is returned instead of creating a duplicate. It also discloses the important behavioral constraint that no checks execute until setup completes, which goes beyond the annotations.

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?

Three tight sentences, front-loaded with the core purpose, then the return value/precondition, then the dedupe rule. Nothing is padded and each sentence carries distinct information.

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 3-parameter mutation tool with no output schema, the description compensates by describing the return (site + setup step), the operational precondition, and the idempotent dedupe path. An agent has enough to call it correctly and interpret the result.

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 description coverage is 100%, so url, name, and platform are already documented in the schema, including the platform enum semantics. The description's note that domain verification is the only option for non-WordPress sites largely restates the platform field and adds no syntax or format detail beyond it.

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 clear verb and resource ('Start monitoring a website') and explains what the call produces (the site plus the required setup step). It gestures at the verification/plugin workflow that sibling tools like verify_site handle but never names those siblings, so differentiation is implicit rather than explicit.

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 conveys the precondition context (no check runs until the owner completes plugin connection or domain verification) but never states when to call this versus add_checks, verify_site, or update_check, nor any exclusion or prerequisite ordering for the agent itself. Usage is implied rather than prescribed.

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