get_sdwan_status

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

The description adds no behavioral context beyond the readOnlyHint annotation. It doesn't mention any side effects, permissions, or constraints such as whether SD-WAN must be configured or what aspects of status are returned, so the annotation remains the only safety-related disclosure.

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, direct phrase with no unnecessary words. It is front-loaded and appropriately sized for a tool with no parameters and a clear purpose, though it lacks additional detail.

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?

The description is minimal and adequately identifies the tool's function, but it lacks usage context and differentiation from similar status tools. The readOnlyHint and output schema help, but the description alone does not provide enough information for an agent to confidently choose this tool over alternatives in all situations.

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?

With zero parameters in the input schema, the baseline is 4. The description adds no parameter information, but none is needed. The schema fully documents that there are no parameters, so no further explanation is required.

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 '获取 SD-WAN 智能组网状态' precisely states the tool retrieves SD-WAN intelligent networking status, providing a specific verb-resource mapping. It distinguishes this from sibling tools like get_wan_status and get_system_overview by explicitly mentioning SD-WAN.

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. The description says nothing about use cases, prerequisites, or when not to use it, leaving the agent without contextual decision support.

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