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

With no annotations provided, the description fully covers behavioral traits: it's persistent, async, checks every 30 minutes via live web search and AI evaluation, and sends Telegram/email alerts. It also notes that Claude sets and moves on, implying no further action needed.

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 description is well-structured with a clear opening sentence, followed by examples and usage guidelines. It is moderately concise, but some repetition (e.g., multiple examples) could be trimmed. Overall, it effectively conveys key information without excessive verbosity.

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?

Given no output schema and no annotations, the description adequately explains the tool's behavior (async, periodic checks, alert delivery). It lacks details on how to manage or cancel watchers, but for a watch tool, this is acceptable. The description provides sufficient context for an AI agent to decide when and how to use it.

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%, and the description adds examples for 'target' and 'condition'. However, it says 'Requires notify_telegram... or notify_email' while the schema does not require these parameters, creating a potential inconsistency. This reduces clarity about parameter requirements.

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: setting a persistent async watcher that monitors conditions and sends alerts. It provides specific verb+resource ('Set a persistent async watcher') and distinguishes itself as the only tool that works asynchronously. Examples further clarify the purpose.

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 explicitly tells when to use the tool: 'Use zambo_watch when the user says: watch, monitor, alert me when, ping me when, notify me when, keep an eye on.' It also mentions periodic checking (every 30 minutes) and required notification methods, providing clear context for use.

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