browser_fingerprint

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

Since no annotations are provided, the description carries the full burden. It discloses the specific properties modified (navigator.webdriver, plugins, languages, chrome.runtime, user-agent), which is solid behavioral insight. It does not mention persistence or reversibility, so it isn't fully comprehensive.

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?

Two concise sentences with no redundancy; the first gives the purpose and the second elaborates on the mechanism. Highly front-loaded and efficient.

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?

For a zero-parameter tool with no output schema, the description covers the action, rationale, and specific behaviors. Minor gaps include not noting session persistence or interaction with other tools, but for the simplicity, it's nearly complete.

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 is empty (0 parameters), so there's nothing to explain. The description appropriately focuses on behavior. With no parameters, the baseline is 4.

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 the specific verb 'Apply' and names the resource 'browser fingerprint,' clearly distinguishing it from navigation and DOM manipulation tools like browser_goto and browser_click. It also enumerates the exact properties normalized, leaving no ambiguity about the tool's scope.

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?

It explicitly states the intended context: 'in CI/testing' and the goal 'to reduce false-positive automation detection.' While it doesn't list alternatives or exclusions, the stated use case is enough for an agent to decide when to invoke it.

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