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

With no annotations, the description carries the full burden. It does disclose real behavior: monitors schedule future network checks, can fire email/webhook notifications, retain predecessors for diffing, and return the created monitor. It omits credit cost, auth/plan requirements, and default scheduling behavior for a 15-parameter creation tool.

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 paragraphs, front-loaded with the core purpose before the form variants. Dense but nearly every clause carries information; the body-form enumeration is slightly list-like but 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 15-parameter creation tool with nested body, no annotations, no output schema, and zero schema descriptions, the description leaves too much undocumented — notably scheduling, notification targets, and result-limiting parameters an agent must set to create a useful monitor.

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 0%, so the description must compensate and only partly does: it explains goal (required in simple form), page/pages, queries and their precedence, and the body escape hatch. Ten of the fifteen parameters (name, email, timezone, maxResults, webhookUrl, includeDiffs, scheduleText, searchWindow, includeDomains, excludeDomains) get no mention at all.

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 and resource ('Create a recurring scrape, crawl, or search monitor') plus its defining behavior (compares each check with its retained predecessor). This cleanly separates it from firecrawl_monitor_get/list/update/run and from the one-off firecrawl_scrape/firecrawl_search siblings.

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?

Explicitly distinguishes the simple form (page/pages or queries plus goal) from the advanced body form, and gives the precedence rule when queries and page/pages are both supplied. It stops short of saying when to prefer this over a one-off scrape/search, but the recurring framing implies it.

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