opn_delete_ddns_account

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

No annotations are provided, so the description carries the full burden. It discloses that the deletion is applied immediately and triggers automatic reconfiguration of ddclient. It also specifies the return format. However, it could mention that the action is irreversible or note permission requirements.

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 three concise sentences, each providing essential information: the action, immediate effect, prerequisite, and return format. No redundant or verbose phrasing. Very efficient.

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?

The description covers the core action, prerequisite steps, behavioral side effects, and return value structure. For a simple one-parameter deletion tool, this is fully complete and aids correct invocation.

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 0%, but the description explains the parameter's purpose ('by UUID') and directs the user to list DDNS accounts to find it. This adds meaningful context beyond the schema's type-only definition.

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 the action 'Delete a Dynamic DNS account by UUID'. It distinguishes the tool from siblings like opn_add_ddns_account and opn_update_ddns_account by specifying deletion. The verb and resource are specific and unambiguous.

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 advises using opn_list_ddns_accounts first to obtain the UUID, which is a clear prerequisite. It mentions that deletion is applied immediately with automatic reconfiguration. However, it does not explicitly state when to avoid using the tool (e.g., irreversible action), but the context is sufficient for correct selection.

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