router_get_ddns

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

No annotations exist, so the description carries the full load; it does disclose that a Network Guard safety check exists and that force bypasses it, which is genuinely useful behavioral context. However, it does not explain why the guard exists, what it protects against, or what happens (error vs empty result) when the guard blocks the call.

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?

One front-loaded sentence stating purpose, plus a single line of parameter guidance. No filler or repetition of the tool name.

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?

A read-only getter with an output schema, so return values need not be described, and the one optional parameter is explained. The remaining gap is the absence of any note on guard-blocked behavior or side effects of force, which an agent would need before setting it.

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% and the single parameter has no schema description, but the description compensates by explaining that force bypasses the Network Guard safety check and that it defaults to false. This is close to complete for a one-parameter tool, though it omits the consequence of enabling force.

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 gives a specific verb (Retrieves) and resource (DDNS provider configurations) and enumerates concrete providers (TP-Link Cloud, No-IP, DynDNS), making the scope unambiguous. It does not explicitly contrast with siblings such as router_set_dns, so it stops short of a 5.

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 never states when to call this versus alternatives, nor any prerequisites or exclusions. The only conditional guidance is the force flag's effect, which is a parameter note rather than usage routing.

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