openwisp_delete_cert

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

With no annotations, the description carries the full behavioral burden, and it only restates that this is a DELETE. It does not say whether the operation is irreversible, what happens to dependent config/VPN bindings, or whether it requires special permissions.

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 compact fragments with the action front-loaded and the category tag and endpoint kept as metadata. No wasted prose, though the brevity comes at the cost of useful detail.

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 destructive single-resource operation with no annotations and no output schema, the description is too thin: it omits irreversibility, side effects on related objects, and the delete-vs-revoke decision.

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 single 'id' parameter is documented as 'Certificate UUID or ID' in the schema. The description adds nothing beyond the schema, so the baseline of 3 applies.

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?

Names a specific verb+resource ('Delete a certificate') and the underlying endpoint, so the operation is unambiguous. However, it does not distinguish itself from the sibling openwisp_revoke_cert, a meaningful PKI distinction an agent needs to make.

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?

No when-to-use guidance and no exclusion criteria. The presence of openwisp_revoke_cert as a plausible alternative is left entirely unaddressed, so the agent has no basis for choosing between deleting and revoking.

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