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

With no annotations, the description carries the full disclosure burden and does so substantively: baseline-on-subscription, check frequencies, visible-text change measurement, recording of every check, webhook behavior, and per-URL pricing. It omits payment/refund/cancellation mechanics, but those are less central to invoking the tool correctly.

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?

Four concise sentences, each carrying a distinct fact: purpose/frequency, change-detection behavior, recording/webhook, and pricing. Front-loaded and free of 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?

Strong on purpose and behavior, but since there is no output schema and no annotations, the description does not say what the call returns (e.g., subscription ID or confirmation), the default duration when duration_months is omitted, or how the urls list should be delimited. For a paid subscription-style tool, these are meaningful 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?

Schema coverage is 60%, and the description compensates by explaining re-check intervals, webhook behavior, and $10/URL/month pricing. It still does not clarify the expected string format for urls or the default if duration_months is omitted, but it adds meaning beyond the bare schema.

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 action and resource: 'Continuous monitoring of public web pages with change detection.' The phrase 'continuous monitoring' clearly distinguishes this from one-off fetching/scraping, especially relative to the sibling hsh-web-scrape.

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?

Clearly conveys the intended use case: pages are baselined on subscription and re-checked hourly, daily, or weekly. It does not explicitly name alternatives or say when not to use the tool, but the continuous-monitoring context is unambiguous.

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