run_browser_info_diagnostic_tool

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

No annotations are provided, so the description must carry the behavioral disclosure burden. It states the action but does not disclose potential side effects, whether it requires an active browser session, how data is handled, or whether saving to file impacts the environment. This lack of detail is a significant gap for a diagnostic tool.

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 a single concise sentence with no fluff, but it is under-specified. It earns its place by stating the core action, yet omits crucial details about usage and parameters, making it too terse for effective tool selection.

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 annotations and the presence of an output schema, the description still fails to provide complete context. It does not explain what makes this tool different from similar diagnostics, how the parameters affect behavior, or any operational prerequisites, leaving the agent with significant ambiguity.

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 input schema has no property descriptions (0% coverage), and the tool description does not mention 'extra_args' or 'save_to_file' at all. The parameter names give some hints, but without any elaboration, the agent cannot correctly decide how to use them.

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 ('Collect browser fingerprint telemetry') and specifies the script path, giving a specific verb and resource. It is distinguishable from sibling diagnostic tools like run_challenge_diagnostic and run_bot_surface_diagnostic by its focus on fingerprint telemetry, though it does not explicitly name alternatives.

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 offers no guidance on when to use this tool versus the many browser-oriented sibling tools. It does not mention prerequisites, typical scenarios, or exclusions, leaving the agent to infer usage from the tool name alone.

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