changedetection_add_notifications

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

Goes beyond annotations by disclosing the dry-run preview path and that tokens are redacted in preview output — meaningful for a write tool. Annotations already flag readOnly=false, idempotent=false, openWorld=true, but the description does not mention that repeated adds are non-idempotent or what permission is 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?

Four terse sentences, purpose front-loaded, then endpoint, then the dry-run caveat and the redaction caveat. Nothing redundant.

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 two-parameter write tool with full schema coverage and no output schema, the description covers purpose, dry-run safety, and output redaction adequately. The main omission is add-vs-replace semantics for existing notification configs, which matters for a non-idempotent write.

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 the schema already documents both parameters including the confirm dry-run semantics and Apprise URL format. The description restates the confirm behavior and adds the redaction note, which is only marginal value over 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?

States a specific verb and resource ("Add global notification URLs") and the backing endpoint. "Add" implicitly contrasts with the sibling changedetection_replace_notifications and changedetection_delete_notifications, but the description never pins that contrast down explicitly.

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?

It explains the dry-run mechanism (omit confirm) but gives no guidance on when to choose add over replace_notifications, or what happens to existing notification URLs when adding. Usage context is only implied.

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