clash.optimize.streaming

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

With no annotations, the description fully discloses read-only nature, scope (rule coverage + probes), and reporting (layer-by-layer). Also clarifies limitations. No annotation contradiction.

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?

One dense paragraph front-loaded with purpose. Every sentence adds value: version, read-only, specific services, layer-by-layer reporting, and explicit exclusions. No waste.

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?

No output schema, but description covers purpose, behavior, and limitations sufficiently for a diagnostic tool. Parameter details are in schema. Minor gap: no mention of result format or pagination, but given 2 params and no nested objects, it's adequate.

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 covers both parameters with descriptions (100% coverage). The tool description adds no additional parameter context. Baseline 3 is appropriate as schema does the heavy lifting.

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 uses a specific verb ('diagnoses') and resource ('streaming service network reachability'), lists exact services (Netflix, Disney+, Prime Video), and distinguishes from siblings by targeting streaming optimization.

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?

Explicitly states what the tool does NOT do (unlock, bypass DRM, modify account) and clarifies that DRM/region issues are not network failures. Provides clear context for when to use, though lacks direct sibling differentiation.

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