run_challenge_diagnostic

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It merely lists script mappings and does not state what the diagnostic run actually does (e.g., launching a browser, visiting the target site, or producing artifacts), nor does it mention side effects or output behavior. This is a significant transparency gap for a tool with 21 parameters and no annotation safety net.

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 exceptionally concise, front-loaded with the primary action, and uses a clear two-line mapping for the mode parameter. Every sentence provides useful information without wasted words, making it easy to parse.

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?

Despite the tool's high complexity (21 parameters, output schema, no annotations), the description is minimal and does not cover the tool's overall workflow, side effects, or how the two modes differ beyond the script they invoke. While the output schema may explain return values, the description still lacks the contextual information needed to use this tool effectively.

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 description coverage is 0%, and the description only adds meaning for the 'mode' parameter (mapping it to scripts). The other 20 parameters, including 'browser', 'headless', 'variants', 'save_artifacts', and 'timeout_ms', receive no semantic explanation, so the description fails to compensate for the low schema coverage.

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 tool's function ('Run target-site diagnostics') and specifies two distinct modes ('toolkit-native or matrix smoking-gun mode'), which gives it a specific resource and behavior. However, it does not explicitly differentiate from sibling diagnostic tools like run_bot_surface_diagnostic or run_browser_info_diagnostic_tool.

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 provides usage guidance for the mode parameter by mapping mode=toolkit and mode=matrix to specific scripts. It does not, however, explain when to choose this diagnostic tool over alternatives, nor does it mention any exclusions or prerequisites, leaving the broader use-case context implicit.

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