run_complete_test

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

With no annotations, the description should fully disclose behavior. It outlines the test steps (download, upload, latency, jitter) and the incremental approach, but lacks details on potential side effects, time consumption, or failure modes.

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 well-structured with a brief title, a paragraph on approach, and an Args/Returns section. Some phrases (e.g., 'inspired by SpeedOf.Me') are slightly extraneous, but overall concise.

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 the absence of an output schema, the description should fully explain return values. It mentions 'download, upload, latency and jitter metrics' but lacks details on format, units, or structure. Parameter documentation is adequate but not exhaustive.

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 description adds basic meaning to parameters (e.g., 'max_size: Maximum file size to test') but does not cover all nuances (e.g., format of max_size string). With 0% schema coverage, it partially compensates but remains incomplete.

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 'Run a complete speed test returning all metrics in a single call', specifying the action and resource. It distinguishes itself from siblings like 'measure_download_speed' by emphasizing comprehensiveness.

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 use for obtaining all metrics at once but does not explicitly state when to choose this over individual measurement tools or provide exclusion criteria. Usage context is implied but not explicit.

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