unifi_run_speedtest

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'Trigger a WAN speedtest' but does not disclose potential side effects (e.g., impact on network performance during the test), duration, or what the return value contains. This is a significant transparency gap for an action that may interfere with network operations.

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 sentence of nine words: 'Trigger a WAN speedtest directly on the UDM Pro gateway.' It is front-loaded with the verb 'Trigger' and contains zero filler words. Every word provides value, making it exceptionally concise and well-structured.

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 tool has no parameters and no output schema, so the description must clarify the return value or outcome. 'Trigger' is ambiguous—it could mean just starting the speedtest or returning the results. The description does not state what the agent should expect as a result, leaving room for misinterpretation. For a simple action, this is adequate but not fully complete.

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 has zero parameters, so the schema fully covers the input space. The baseline for 0 params is 4, and since there are no parameters to explain, the description does not need to add parameter semantics. It correctly omits any param-related details.

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 clearly states the specific action: 'Trigger a WAN speedtest directly on the UDM Pro gateway.' It uses a specific verb ('Trigger') and resource ('WAN speedtest on UDM Pro gateway'), which uniquely distinguishes it from all sibling tools in the UniFi management suite.

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 implies when to use it (when you want to run a speedtest on the gateway) but does not explicitly state alternatives or exclusions. The phrase 'directly on the UDM Pro gateway' provides context that this is device-specific, but there is no guidance on when not to use it or alternative methods for measuring network performance.

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