changedetection_delete_notifications

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is known. The description adds genuinely useful behavior beyond that: the endpoint is DELETE-with-JSON-body (unusual and worth calling out) and omitting confirm yields a dry-run preview rather than an error. It does not describe the return payload, which keeps it below a 5.

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 short, front-loaded sentences: the action first, then the transport detail, then the dry-run caveat. No filler and nothing buried.

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?

No output schema exists, so the description could state what a successful delete (or dry-run) returns — e.g. how many notifications matched or were removed. It also does not clarify whether watch-scoped subscriptions are affected by 'global'. Adequate for invocation, thin for interpreting results.

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%, so the schema already documents both parameters in detail, including that confirm must be the boolean true and that false/string 'true' are rejected. The description's dry-run note restates what the schema says, adding no new semantic detail — the baseline 3 applies.

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 names a specific verb and resource ('Delete matching global notification URLs'), which separates it from per-watch notification handling and from its siblings add_notifications/replace_notifications/list_notifications. It does not explicitly name the sibling it is not, but 'global' plus 'delete' pins the operation clearly.

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 dry-run hint ('Omit confirm for a dry-run') gives real operational guidance about how to invoke safely, but the description never says when to choose this over replace_notifications or per-watch operations, and gives no prerequisites. Usage is implied rather than stated.

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