Dismiss all persistent notifications

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

Annotations declare idempotentHint=true and destructiveHint=false, and the description adds that the call is made over HTTP with no data and that it affects every currently shown banner. It does not state reversibility (dismissed banners are gone) or required auth. Useful addition beyond annotations, but not exhaustive.

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 short, front-loaded segments: action, transport, when-to-use, not-for, return. Every sentence earns its place and the routing information comes early.

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 idempotent dismissal with an existing output schema, the description covers purpose, routing, transport, and return type. It omits minor details like the exact result shape or auth requirements, but an agent has enough to call it correctly.

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?

Parameter count is 0, which gives a baseline of 4. The description correctly notes the service is called with no data, reinforcing that no parameters are expected. No additional parameter meaning exists to add.

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+resource: 'Dismiss every persistent notification currently shown in the Home Assistant UI.' It also names the underlying service call, removing ambiguity. Distinguishes from sibling services_notify_persistent_dismiss by scope (all vs single).

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?

Explicit when-to-use section ('clearing all UI banners at once') and an explicit not-for section routing the agent to the single-dismiss sibling. Nothing is left to inference.

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