services_send_notification

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

No annotations are provided, and the description does not disclose behavioral traits such as permissions required, failure modes, or asynchronicity. This leaves the agent with incomplete understanding of the tool's safety and side effects.

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, which is concise, but it lacks structure (e.g., no separate parameter group). It efficiently states purpose but misses opportunities to organize information clearly.

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?

Despite having an output schema signal, the description does not explain return values. With 3 parameters (only target partially explained) and no annotations, the description is incomplete for an agent to fully understand the tool's behavior.

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 0%, so the description must add meaning. It only explains the 'target' parameter's purpose and default, leaving 'message' and 'title' semantically bare. This is insufficient for proper parameter usage.

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 it sends a Home Assistant notification, with a specific verb and resource. It distinguishes from siblings like services_notify_persistent_create by focusing on the basic notify service. However, it could be more precise about the notification channels (e.g., mobile push).

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 provides a hint about the target parameter default ('notify service name'), implying it's the main notification tool. But it lacks explicit when-to-use or when-not-to-use guidance compared to alternatives like persistent notifications.

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