list_dynamic_dns

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

With no annotations, the description carries the behavioral disclosure burden. It goes beyond the tool name by warning that the response is 'Returned verbatim, including plaintext x_password credential fields,' which is a significant, non-obvious behavioral trait. It does not cover auth or rate limits, but the plaintext credential warning is high-value context.

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 compact and front-loaded: the first sentence states the core purpose, the second explains parameters, and the third adds a security-relevant return trait. Every sentence earns its place with no redundancy.

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 two-parameter list tool with no annotations and no output schema, the description covers the purpose, all parameter formats, and a notable plaintext-credential response detail. It does not spell out the exact output shape or pagination, but the description provides enough for a 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 description coverage is 0%, and both parameters are unannotated strings. The description fully compensates by specifying accepted forms for each: host is 'console name, ID, or composite ID (MAC:numericId format)' and site is 'site name or ID.' This gives the agent all the semantic meaning the schema lacks.

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 and resource: 'List Dynamic DNS provider configurations for a site.' This clearly identifies what the tool does and distinguishes it from related siblings like get_dynamic_dns and update_dynamic_dns with the plural action 'List' and site scoping.

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 gives clear context ('for a site') and implies the tool is for listing configurations, but it does not explicitly say when to choose this over get_dynamic_dns or update_dynamic_dns, and it offers no exclusions or alternatives. Usage is implied rather than explicitly guided.

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