nab

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

Annotations cover safety profile (readOnly, non-destructive, open-world). Description adds valuable behavioral specifics: lists exact test protocols performed and notes that results include timing data. No contradictions with annotations.

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?

Excellent structure with three distinct, compact lines covering action, test scope, and return values. No wasted words; front-loaded with the core verb and target.

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?

Adequate for a zero-parameter tool with existing output schema. Description appropriately avoids redundant return value details (covered by schema) while still noting the timing aspect. Safety profile covered by annotations.

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?

Baseline score of 4 applies as there are zero parameters requiring semantic explanation. The schema is empty object, requiring no additional parameter context from the description.

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?

Specific verb 'Run' with clear resource 'validation tests against real websites'. Lists specific test categories (HTTP/2, HTTP/3, TLS 1.3, 1Password) that clarify scope. However, lacks explicit distinction from sibling 'fingerprint' tool which overlaps with the 'fingerprinting' test mentioned.

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?

Provides implied usage guidance through enumeration of specific test types (HTTP/2, compression, TLS, etc.), suggesting when to invoke based on validation needs. No explicit comparison to siblings like 'benchmark' or 'fingerprint' to clarify selection criteria.

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