opnsense_acme_delete_cert

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

No annotations provided. Description conveys mutation but adds no extra behavioral context such as irreversibility, permission requirements, or side effects beyond the basic delete action.

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 sentences with no fluff. First sentence states purpose, second gives a critical follow-up action. Every word earns its place.

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 simple delete-by-UUID tool, the description is fairly complete. It mentions the follow-up apply step. However, missing details like what happens if UUID doesn't exist or confirmation of success, but given simplicity, it's adequate.

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 100% and the schema describes 'uuid' as 'UUID of the certificate to delete'. The tool description adds no new meaning beyond what the schema provides, so baseline 3.

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 'Delete an ACME certificate by UUID' which clearly identifies the verb (Delete), resource (ACME certificate), and method (by UUID). It distinguishes from sibling tools like create or list.

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?

Provides a clear follow-up instruction: 'Run opnsense_acme_apply afterwards', which hints at the workflow. However, lacks explicit when-to-use vs. alternatives like renew or why deletion is needed.

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