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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so safety is covered. The description still adds useful substance by enumerating the shape of each preset (id, human-readable title, required and optional params, default schedule), which is real behavioral context beyond the annotations, though nothing about ordering guarantees or caching is mentioned.

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 core purpose, then the definition, then the usage instruction, then an illustrative example. Every block earns its place, though the multi-line example output is somewhat verbose given an output schema already exists.

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?

For a zero-parameter read tool with a complete output schema and full annotation coverage, the description supplies everything needed: what presets are, their field composition, and how to chain into impri_create_watcher_from_preset. No material gap remains for an agent deciding whether and how to call 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?

The tool takes zero parameters, so the baseline of 4 applies. The description correctly explains that no param values are needed at this stage and that params belong to the downstream creation call, which is relevant clarifying context despite there being no schema to complement.

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 and resource ('List all available watcher presets') and immediately clarifies the resource type ('pre-configured watcher templates for common sources'). An agent can distinguish this from the sibling impri_list_watchers because the description defines presets as templates with id/title/params/schedule.

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 says 'Call this first to discover which preset fits your monitoring goal, then use impri_create_watcher_from_preset', giving both the ordering and the named follow-up tool. It also states the payoff ('No deep knowledge of watcher config schemas is needed'), removing ambiguity about when this is preferable to building a watcher manually.

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