pve_notification_endpoint_delete

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

The description clearly marks the tool as a MUTATION, details the dry-run safety mechanism, and warns about the side effect of matchers failing silently. Since no annotations were provided, the description carries the full burden and does a good job disclosing these behavioral traits, though it could elaborate on post-deletion consequences.

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 concise, with three sentences that front-load the tool's mutation nature, then list types, then cover safety and warnings. Every sentence adds value without unnecessary verbosity.

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?

For a deletion tool with four parameters and an output schema, the description covers the essential aspects: action, type, safety, and side effects. However, it omits details about the 'captured current config' output and does not guide on prerequisite actions (e.g., removing matchers first), leaving some completeness gaps.

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 low (25%), and the description adds value by enumerating valid ep_type values (gotify|smtp|sendmail|webhook) and explaining the confirm parameter's role in execution. However, it does not describe the name parameter or provide format guidance, so it only partially compensates for the schema's lack of detail.

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 'delete a PVE notification endpoint' and lists valid ep_type values (gotify|smtp|sendmail|webhook), establishing the tool's specific action and resource. However, it does not explicitly differentiate this from sibling tools like pve_notification_endpoint_update or pve_notification_matcher_delete, which could create ambiguity about when to use each.

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 safety guidance (dry-run by default, confirm=True to execute) but fails to contrast this tool with alternatives. There is no mention of when to use this over pve_notification_endpoint_update or how to handle matchers before deletion, leaving the agent without clear usage boundaries.

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