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

Annotations only declare openWorldHint and destructiveHint=false; the description adds real behavioral context beyond them – defaults (enabled=true, cadence_minutes=60), the credit cost of completed checks, and webhook notifications. The 'modifies stored state' note reinforces the write nature. It stops short of 5 only because it does not detail reversibility, rate limits, or auth requirements.

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?

Front-loaded with the create action and its return value, then defaults, cost, notifications, and alternatives. Sentences are dense and useful, though the tool is on the longer side; nearly every clause 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?

An output schema exists, so the description needn't describe returns, and it correctly focuses on cost, defaults, and sibling routing. It is complete enough for a 7-param nested tool, with only minor gaps around auth/permission prerequisites.

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 100%, so the schema already documents every parameter including the defaults the description restates (enabled, cadence_minutes). The description adds no parameter meaning beyond the schema, so the baseline 3 is appropriate.

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 (Create) and resource (persistent website-change monitor), plus scope: owned by the authenticated principal, watching a page or sitemap on a schedule, returning its configuration and id. This clearly distinguishes it from the sibling monitors_list, monitors_get, monitors_update, monitors_delete and monitors_checks.

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 routes the agent: 'Use monitors_list to find existing monitors before creating another, or monitors_update to change one.' Both the when-to-use and the named alternatives with their selecting conditions are given, leaving nothing to inference.

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