unifi_gen_listsdwanconfigs

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered without the text. The description adds only the upstream provenance (developer.ui.com site-manager v1 listsdwanconfigs endpoint), which is mild but genuine extra context; nothing about result volume, pagination or filtering is disclosed.

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?

A single front-loaded clause names the action and resource before any noise. The trailing source-endpoint string is machine-generated provenance — mildly useful but not agent-actionable, which keeps it out of 5 territory.

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 no-argument read-only list tool with annotations covering safety and no output schema, the description is minimally sufficient to invoke it. However, it never says what an SD-WAN config contains, whether the list is site-scoped, or whether results are paginated, leaving real ambiguity that the annotations cannot fill.

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?

The tool takes zero parameters, so per the baseline this is a 4. The description introduces no parameters that could be misread or left ambiguous.

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+resource ("List SD-WAN Configs"), so an agent immediately knows this is a read operation over SD-WAN configuration objects. It does not differentiate from near-identical siblings such as unifi_sm_list_sdwan_configs or unifi_gen_getsdwanconfigbyid, which prevents 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?

There is no when-to-use or when-not-to-use guidance and no alternative tool is named. An agent must infer the scope purely from the tool name, with no help on choosing between this and the other SD-WAN list/get tools.

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