lucky_delete_ddns

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

The annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false. The description simply restates 'Delete' without adding behavioral context such as whether deletion is permanent, cascading, or silently ignores missing keys.

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 a single, front-loaded sentence with no wasted words. It immediately states the action, the target, and the selection mechanism.

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?

This is a simple tool with strong annotations covering the destructive and idempotent nature, so the description does not need to repeat those. However, without an output schema or explanation of the key's origin, an agent may not know enough to call it correctly in edge cases.

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?

The only parameter is 'key', and 'by key' adds the basic meaning that the key selects which DDNS entry to delete. However, schema description coverage is 0%, and the description does not explain where the key comes from or what format it follows.

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 uses a specific verb ('Delete') and names the resource ('Lucky ddns'), with 'by key' indicating the selection method. It is clear enough to distinguish from create/update/list ddns tools, though it does not explicitly contrast with sibling delete tools.

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?

There is no guidance about when to use this tool, prerequisites, or how it relates to alternatives such as lucky_create_ddns or lucky_update_ddns. The agent must infer usage entirely from the tool name and sibling context.

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