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

With no annotations, the description carries the full disclosure burden. It does add real behavioral context — checks run every ~5 minutes, alerts go to Slack/Discord/Telegram, and a public status page is created (a privacy-relevant detail). However, it never says whether this sets up a persistent recurring job on the server, what the call returns (e.g., a monitor ID or status page URL), how to stop it, or that a pro key is required for more than 3 URLs.

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 core capability and limits are front-loaded in one dense sentence, with the pricing/upgrade detail relegated to a second sentence. The promotional content is slightly noisy but does convey the practical URL cap and key source, so it largely earns its place.

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 5-parameter mutation-style setup tool with no output schema and no annotations, the description covers purpose and quota but leaves the agent without a picture of the lifecycle: whether monitors persist, what is returned, or how they are later managed. Adequate, but with clear gaps for something that seeds a background service.

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?

At 60% schema coverage the description usefully fills gaps: it explains the 3-URL ceiling (urls), enumerates the accepted alert destinations (webhook), and gives the pro_key format ('UP-...') and where to obtain it — none of which is documented in the schema for pro_key. It does not explain chat_id requirements for Telegram beyond what the schema already says.

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 description names a specific verb and resource — 'Monitor up to 3 URLs every ~5 minutes and send DOWN/UP alerts' — which clearly distinguishes this tool from the one-shot siblings check_website and check_websites. It doesn't explicitly name those siblings as alternatives, but the recurring-monitoring plus alerting framing makes the distinction obvious.

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?

Usage is only implied: the agent must infer that this is for persistent, alerting-based monitoring rather than a one-off check. The 3-URL cap and the Pro upgrade path give some practical context for choosing it, but there is no explicit 'use this when…' statement, no exclusions, and no named alternatives.

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