notify_one

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

With no annotations, the description must disclose behavior. It states that notifications are not persisted, which is a key behavioral trait. However, it does not mention error handling, rate limits, or whether the tool is synchronous. The existence of an output schema suggests a return value, but the description omits any discussion of results.

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-loading the core purpose in the first sentence and usage guidance in the second. Every word adds value, with no redundancy or filler.

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?

The tool is simple and the description covers purpose and usage context. However, it omits parameter semantics (despite low schema coverage) and does not explain the output format, even though an output schema exists. For a tool with 4 parameters and no schema descriptions, the description is incomplete.

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?

The schema has 0% description coverage, and the description does not explain individual parameters. It only loosely associates 'ad-hoc Apprise URL' with the 'url' parameter, but provides no details on formats, allowed values for 'severity', or the role of 'body' and 'title'. The description fails to compensate for the missing schema descriptions.

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 that the tool sends a notification to a single ad-hoc Apprise URL and notes that it is not persisted. This distinguishes it from siblings like 'notify' (persisted channels) and 'dry_run' (testing), providing a specific verb-resource-scope combination.

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 explicitly says 'Useful for one-off pages where the channel isn't in `APPRISE_URLS`', giving clear context for when to use this tool. It implies the alternative 'notify' for persisted channels, though it does not name the sibling directly.

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