lucky_delete_certificate

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the destructive nature is covered. The description adds no behavioral context beyond this, such as irreversibility, impact on dependent resources, authentication needs, or error behavior.

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?

A single, direct sentence with no filler or repetition. The operation and parameter role are front-loaded, and 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 tool, the description and annotations provide the core operation and safety profile. However, the meaning of 'key' is underspecified and there is no mention of expected output or side effects, leaving some ambiguity for an agent.

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?

With 0% schema description coverage, the description must compensate for the undocumented 'key' parameter. Saying the certificate is deleted 'by key' indicates the key is the identifier, but it does not explain the key's format, how to obtain it, or its domain-specific meaning.

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 a specific verb (delete), a specific resource (Lucky certificate), and an explicit identifier (key). It clearly distinguishes from sibling delete tools for other resources such as STUN rules, port forwards, web services, and DDNS.

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?

Usage is implied by the operation and tool name, but there is no explicit guidance on when to delete a certificate, how to obtain the key, or any prerequisites. It does not mention alternatives or exclusion conditions, so an agent must infer the intended context.

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