opn_update_ddns_account

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

With no annotations, the description fully discloses behaviors: only provided parameters are changed, ddclient is automatically reconfigured, changes take effect immediately, and return dict includes 'result', 'uuid', 'reconfigure_status'. This meets the full burden.

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?

Efficiently structured: purpose first, then usage context, effect, prerequisite step, parameter list, and return value. No wasted words; each sentence adds value.

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?

Given the complexity (9 parameters, no enums, no nested objects) and presence of output schema, the description covers all necessary aspects: it explains when to use, how to prepare (list first), what happens after update, and what is returned. The sibling tools list is large but the description focuses on its own purpose without needing explicit comparisons.

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 description lists all 9 parameters with brief explanations (e.g., hostname: 'fully qualified domain name'). While it lacks detailed format or enum lists, it provides sufficient meaning beyond the schema for most parameters. Examples given for some values (e.g., 'cloudflare', 'web_dyndns') help.

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 verb 'Update', the resource 'Dynamic DNS account', and specifies 'by UUID'. It distinguishes from sibling tools like opn_add_ddns_account and opn_delete_ddns_account by the update action and applying configuration.

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 explicit usage context: 'Use this when you need to change...' and recommends using opn_list_ddns_accounts first to find the UUID. Does not explicitly state when not to use, but the sibling tools cover create/delete/list/reconfigure separately, making the guideline clear.

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