pve_notification_test

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

With no annotations, the description carries full burden. It explicitly warns 'MUTATION' and 'SENDS A REAL NOTIFICATION — recipients will receive it', disclosing the dangerous behavior. However, it does not mention auth requirements or error handling.

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?

Two concise sentences cover mutation, dry-run, execution flag, and real send warning. Every word adds value; no fluff or redundancy.

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 description covers mutation, dry-run, and real notification risk. With an output schema present, return value detail is not needed. However, it lacks mention that the name must be an existing target and does not describe dry-run behavior (simulation vs no-op).

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 low (33%), but the description adds meaning for the confirm parameter (dry-run default, confirm to execute). It does not clarify the name parameter, leaving its semantics implicit beyond the schema type.

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 states the verb 'send a test notification' and the resource 'PVE notification target', clearly distinguishing it from sibling tools like pve_notification_endpoint_create. The phrase 'SENDS A REAL NOTIFICATION' further clarifies its purpose.

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 explains the dry-run default and tells users to set confirm=True to execute. While it lacks explicit 'when not to use' guidance, the implications are clear: use dry-run for safe testing, and confirm only when ready to send a real notification.

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