list_dns_servers

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

No annotations are provided, so the description carries full behavioral burden. It does not state that this is a read-only list operation, whether it requires specific permissions, how vdom defaults behave, or what the response structure looks like beyond a brief hint about interfaces and mode.

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 fragment rather than a clear, front-loaded action statement. It is short but under-specified for an agent trying to understand the tool's operation and structure.

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?

With no annotations and no output schema, the description is the main source of behavioral context. It only vaguely describes returned content and omits usage context, read/write safety, and operational details, leaving significant gaps for an agent.

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 100% for the single vdom parameter, so the schema already documents the parameter including its default. The description adds no additional parameter meaning, which matches the baseline of 3 when schema coverage is high.

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 names the resource being returned (interfaces where FortiGate answers DNS queries) and adds the mode detail, so the subject is identifiable. However, it is a noun phrase with no explicit verb indicating a list/retrieve operation, and it does not distinguish this tool from siblings such as get_dns_settings or list_dns_zones.

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 on when to use this tool versus alternatives like get_dns_settings, set_dns_server, or delete_dns_server. The description provides no context, prerequisites, or exclusions.

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