Add Ddns

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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses nothing about authentication/credential handling (username/password are required), provider requirements, or whether a duplicate domain is rejected. This is a multi-parameter mutation with zero behavioral disclosure.

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?

It is short, but this is under-specification rather than conciseness; the single phrase conveys no actionable information. Nothing is front-loaded because there is nothing substantive to front-load.

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?

Although an output schema exists so return values need not be documented, the description leaves a 6-parameter, 4-required mutation with no annotations totally unexplained. It is far too thin for the complexity of the tool.

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 description coverage is 0% across 6 parameters (domain, provider, username, password, enabled, interface), and the description adds no meaning for any of them. Critically, the expected format for 'provider' and 'domain' is left entirely unexplained, so the agent cannot populate them correctly.

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 '添加 DDNS' (Add DDNS) merely restates the tool name add_ddns and title 'Add Ddns' in another language. It identifies no resource details, scope, or any distinguishing feature versus siblings like get_ddns_config, delete_ddns, or get_dynamic_dns_config.

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, no prerequisites, and no mention of alternatives such as get_ddns_config or delete_ddns. An agent gets zero help deciding when this tool is appropriate.

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