browser_fingerprint_check

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

With no annotations provided, the description must carry the full behavioral burden. It only states that it 'collects' diagnostics, but does not disclose whether this is a pure read operation, whether it may trigger any browser events, how much data is collected, or what the returned structure looks like.

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?

A single sentence, front-loaded with the action and target resource. There is no extraneous detail or repetition, making it efficient and 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?

The tool is simple with no parameterscustom, and the description is understandable for selecting the tool. However, without an output schema or any description of the returned fingerprint values, the agent does not know what to expect from the call, leaving a moderate gap.

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 tool has zero parameters samanage, so parameter semantics are not applicable. The baseline of 4 is appropriate because no additional parameter documentation is needed and the description does not mislead about parameters.

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 identifies the verb ('Collect') and the resource ('browser fingerprint diagnostics from the active page'). It is distinguishable from typical navigation, storage, and visibility tools in the sibling list, though the exact meaning of 'fingerprint diagnostics' could be slightly more explicit.

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 gives no indication of when to use this tool versus alternatives like browser_evaluate, browser_get_visible_text, or browser_network_requests. There is no mention of context, prerequisites, or exclusions, leaving the agent to infer the appropriate usage scenario.

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