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

With no annotations, the description carries the full burden and discloses substantial non-obvious behavior: timezone handling rules, the 7-day backfill window constraint, plan-dependent minimum frequency, and the removal of inline webhook config. It does not cover auth/permission requirements or whether creation triggers an immediate first run, which keeps it below 5.

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?

Purpose is front-loaded, followed by a workflow note and a scannable bulleted list of constraints. Every section adds non-redundant value beyond the schema; the length is justified given the number of operational gotchas for an 8-parameter tool.

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?

Output schema covers return values, and the description covers the failure-prone operational details (timezone, backfill window, webhook centralization, plan limits). Minor gaps remain around auth requirements and whether the monitor executes immediately on creation, but for a complex tool with no annotations this is strong.

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 100%, setting a baseline of 3. The description adds meaning beyond the schema for schedule/timezone (always include a timezone; schedule text overrides the arg), backfill (7-day end_date constraint), and webhook_ids (register with create_webhook first; no inline config).

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?

Opens with a specific verb + resource + source: 'Create a recurring monitor from a completed job.' The second sentence ('Monitors re-run a job's query on a schedule') pins down what a monitor is, clearly distinguishing this from siblings like create_webhook, update_monitor, disable_monitor, or submit_query.

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?

Gives explicit workflow positioning: 'Use the explore -> refine -> automate pattern: submit a job, refine until results match, then create a monitor.' It also routes webhook setup to the create_webhook sibling. It stops short of a 5 because it never explicitly says when-not-to-use this in favor of update_monitor/disable_monitor/delete_monitor.

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