services_notify_persistent_create

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

With no annotations, the description carries the burden. It discloses that the tool creates/replaces (write operation) and that providing notification_id enables later management. However, it does not detail side effects, permissions, or exactly what 'persistent' entails (e.g., surviving restarts).

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?

The description is two sentences, front-loaded with the primary purpose, and provides essential usage guidance without redundancy. Every sentence adds value.

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?

Given the tool's simplicity and presence of an output schema (context signal), the description covers the main use case and parameter hints. It could mention the replacement behavior explicitly, but 'Create or replace' implies it. Overall sufficient for correct invocation.

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?

With 0% schema description coverage, the description adds critical context for notification_id, explaining its purpose for dismissal/update. While message and title are self-explanatory, the description compensates adequately for the low coverage.

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 clearly states 'Create or replace a persistent notification in the HA UI.' The verb and resource are specific, and mentioning HA UI provides context. It differentiates from sibling tools like services_notify_persistent_dismiss by explaining the use of notification_id for later dismissal.

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 description advises using notification_id for future dismissal/update via notify_persistent_dismiss, guiding when to use that parameter. However, it does not explicitly contrast with alternatives like services_send_notification, but the naming makes the use case clear.

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