impri_create_watcher

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

Discloses key behaviors: first run establishes baseline (no alerts), deduplication by URL/content-hash, delivery to inbox/webhook, and return object. Without annotations, this is a good level of transparency.

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?

Description is concise and well-structured: purpose, details, then example. Every sentence adds value with no redundancy 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?

Covers creation, scheduling, deduplication, first-run behavior, and return value. Lacks error handling or permission requirements, but overall complete for a create tool given no output schema.

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 only describes 'spec' as a backup reference to SPEC.md. The description adds a detailed example with all fields (name, kind, config, keywords, etc.), significantly enhancing understanding beyond the schema.

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?

Description clearly states the verb 'Create' and resource 'watcher', and distinguishes from sibling tools like 'impri_list_watchers' and 'impri_create_watcher_from_preset'. The example and return value 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?

Description explains when to use this tool (monitor external sources) and provides details on scheduling and deduplication. It does not explicitly mention when not to use it or alternatives, but the sibling tools imply a differentiation.

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