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

With no annotations provided, the description carries the full burden and delivers: it discloses the audit frequency ('about once a day'), the exact alert triggers ('drop of more than 5 points, or falling below the 85 client-ready bar'), and the alert method ('emails'). This is exceptionally transparent for a watch-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?

Three sentences, front-loaded with the primary action, then key behavior, then a concrete use case and limit. Every sentence adds value and there is no repetition or fluff.

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?

The description covers the purpose, usage scenario, behavioral details, and constraints (Pro requirement, limit of 10). With no output schema and simple parameters, this is complete enough for an agent to decide when to invoke and what to expect.

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%, with both 'url' and 'email' having clear descriptions. The tool description adds no additional parameter-level details, so the baseline of 3 is appropriate. It does not need to compensate for schema gaps.

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 clearly states the tool's purpose: 'Watch a live site's design score' and explains the monitoring behavior (re-audits daily, emails on regression). This distinguishes it from siblings like list_watches and unwatch_site, and the specific thresholds make it unambiguous.

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?

The description provides explicit usage context: 'Use it right after shipping a client site so a broken deploy is caught before the client sees it.' It also notes the license limit of 10 active watches. It does not explicitly mention alternative tools or when not to use it, so it falls short of a 5.

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