list_sdwan_configs

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

No annotations are provided, so the description carries the behavioral burden. It discloses non-obvious behavior: default drains all pages, capped drain returns incomplete=true rather than truncating silently. This is valuable beyond what the input schema shows. It doesn't explain response structure or rate limits, but the output schema handles return format, so this is adequate.

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 three short paragraphs, front-loaded with a clear statement of purpose, then precise pagination behavior. Every sentence earns its place; no filler or 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?

Given a simple one-parameter tool with no annotations but an output schema, the description covers the resource, default behavior, and pagination semantics. It doesn't mention required permissions or limitations, but the tool is a read-only list with one optional parameter, so the description is complete enough for an agent to invoke it correctly.

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%, so the description must compensate. The description explains page_token's role: passing it fetches a single page manually, and the response carries a nextToken cursor. This adds meaning beyond the schema's raw type definition.

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 Site Magic (SD-WAN) VPN mesh configurations.' It distinguishes from sibling list tools by focusing on SD-WAN configs and mentions pagination behavior. The title is null, but the description makes the purpose clear.

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?

It explicitly explains when to use the default behavior (every page drained, complete list returned) and when to pass page_token to fetch a single page manually. The nextToken cursor behavior is described, which guides the agent on iterative pagination.

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