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

Annotations already declare non-read-only, non-idempotent, open-world and non-destructive behavior, so the bar is lower. The description adds genuinely useful context beyond them: presets perform URL building, keyword setup and SSRF validation; name and schedule default to preset values; and the return shape is stated. It does not mention permission requirements or error behavior, keeping it out of the top band.

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 action and the preset-responsibility rationale, then defaults, then return shape, then examples. Every sentence earns its place, though four examples is on the generous side for a tool with only four parameters.

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, yet the description still names the returned fields briefly, and it correctly delegates the open-ended param vocabulary to impri_list_watcher_presets rather than trying to enumerate every preset inline. For a nested-object tool whose param keys are preset-dependent, this is as complete as a description can reasonably be.

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%, so baseline is 3, but the description adds real meaning: it explains that params keys come from the preset listing tool, that schedule is an override of a preset default, and that name defaults to "{preset title}: {primary param value}". The examples show preset-specific param keys (subreddit, owner/repo, keyword/min_points) that the schema's free-form additionalProperties cannot convey.

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 (create a watcher from a preset template) and immediately distinguishes this path from raw watcher construction by explaining that presets handle all config building. It also points at the companion tool impri_list_watcher_presets as the source of valid ids and params, so an agent can separate it from impri_create_watcher.

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?

Gives clear usage context: supply preset_id plus param values obtained from impri_list_watcher_presets, with defaults applied when name/schedule are omitted. Four worked examples show concrete invocation patterns. It never explicitly states when to prefer this over the sibling impri_create_watcher, so it falls short of the top band.

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