scan

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

With no annotations, the description fully explains the ping-and-sort behavior, verification logic, caching, and what BROKEN status means. It lacks details on error handling or rate limits, but covers core behavior well.

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 lead-in, detailed verification note, and bulleted args. It is somewhat lengthy but every sentence adds value; could be slightly more 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 8 parameters and existence of an output schema, the description covers the core functionality, return order, verification behavior, and caching. It does not explain the output structure beyond 'fastest-first', but the output schema likely covers that.

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 provides comprehensive explanations for all 8 parameters, including examples and default values, compensating for the 0% schema description coverage. Each parameter's purpose and valid values are clearly stated.

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 'Ping models in parallel and return ranked results by latency' with a specific verb and resource. It also distinguishes from siblings like 'get_fastest' by mentioning 'ranked list' and 'Use when you need live speed data or a ranked list.'

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 says 'Use when you need live speed data or a ranked list' and notes the time range 'Takes 2-10 seconds depending on filters.' It does not explicitly mention when not to use or alternatives like 'get_fastest', but the context is clear.

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