List SD-WAN configurations

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 elsewhere. The description adds only the 'account-level' scope and says nothing about pagination, result size, or whether an empty result is possible for accounts without SD-WAN — for an open-world read that is the kind of context worth adding.

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 extremely short and front-loaded, but it is a noun-phrase fragment rather than a sentence, and its brevity comes from under-specification rather than tight editing. Nothing is wasted, yet nothing is earned either.

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 output schema, no parameters, and heavy sibling overlap (unifi_gen_listsdwanconfigs, unifi_sm_get_sdwan_config, unifi_sm_get_sdwan_config_status), the description should at minimum say what is returned and how it differs from those siblings. Annotations cover safety, but the selection-critical context is missing.

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 and the schema is empty at 100% coverage, so there is nothing for the description to disambiguate. Baseline 4 applies: no parameter semantics are needed here.

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 fragment "Account-level SD-WAN configurations" names the resource and adds a scope qualifier (account-level) that the title lacks, implying a list. But it omits a verb entirely, so the agent must infer 'list' from the tool name, and it does not distinguish itself from close siblings like unifi_sm_get_sdwan_config or unifi_gen_listsdwanconfigs.

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 versus unifi_sm_get_sdwan_config (single config), unifi_sm_get_sdwan_config_status, or unifi_gen_listsdwanconfigs, despite multiple near-identical siblings. The only hint is the implicit 'account-level' scope, which is left for the agent to interpret.

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