pve_notification_matcher_delete

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

Discloses destructive nature ('MUTATION'), default dry-run behavior, confirm flag, and critical side-effect (alerts un-routed). No annotations provided, so description carries burden. Could mention irreversibility but overall transparent.

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?

Three concise sentences: purpose, usage, warning. Front-loaded with key info. No wasted text.

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?

Covers core behavior, usage, and consequence. Lacks prerequisites (e.g., matcher must exist) or error states, but output schema handles return info. Adequately complete for a simple deletion tool.

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?

Only the 'confirm' parameter is implicitly explained (dry-run default); 'name' and 'proximo_target' are not described beyond schema titles. With 33% schema coverage, description should compensate but does not.

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?

Description clearly states 'MUTATION: delete a PVE notification matcher' – specific verb and resource. Distinguishes from siblings like pve_notification_matcher_set (create/update) and other delete tools (pve_notification_endpoint_delete).

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?

Specifies dry-run by default and confirm=True to execute, guiding safe usage. Includes a warning about consequences (alerts go un-routed). Lacks explicit when-not or alternatives, but the information is sufficient for typical use.

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