Watch a URL for Change

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

Beyond the annotations, it discloses deterministic evaluation, no push delivery, stale-on-failure reporting, dedicated headless session, interval floors and quotas, honoring 429s without retry, and auto-pause on repeated failure. This is exemplary behavioral disclosure and does not contradict readOnlyHint/destructiveHint.

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?

The text is dense but every sentence adds a distinct constraint or behavior, and the most important information about scope is front-loaded. No filler or redundant restatement of the schema.

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?

The behavioral context is unusually complete for a 9-parameter tool with no output schema, and it even hints at report semantics. Yet an agent still cannot fully infer how to create/select a monitor, what `since` and `label` mean, or what the exact response shape is, leaving operational gaps.

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?

With 0% schema coverage, the description must carry parameter meaning, and it does name the four condition values and report/check_now actions while indirectly suggesting url, selector, value, and interval. However, label, since, and monitor remain unexplained, and no parameter requirements per condition are spelled out, so it only partially compensates.

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?

The opening line 'Watches one URL for one deterministic change while this server runs' states a specific action, resource, and scope, and the four condition names make the function concrete. It does not name a sibling for contrast, so it misses the explicit differentiation needed for a 5.

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 description makes the intended use implicit: a long-running watcher for one deterministic page change, with 'report' and 'check_now' as the query/force actions. It never says when to prefer this over siblings like wait_for or get_page_view, so the agent is left to infer tool selection.

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