camofox_evaluate_js

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

No annotations are provided, so the description carries full burden. It discloses isolated scope and safety, but does not explain return value format, error behavior, or potential side effects like page state changes. Adequate but not 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?

Three sentences: purpose, scope, use cases. No filler, front-loaded with key information. Every sentence earns its place.

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 no output schema or annotations, the description covers purpose, scope, and use cases. Minor gap: it does not describe the return value or error handling, which are important for evaluating JS. Otherwise 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?

Schema description coverage is 100%, so baseline is 3. The description adds no semantic meaning beyond the schema; it repeats 'isolated scope' but that's behavioral, not parameter-specific. Examples in schema are good.

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 executes JavaScript in browser context, specifies isolated scope (invisible to page scripts, safe for anti-detection), and distinguishes from siblings by listing specific use cases (extracting data, checking properties, reading styles, manipulating DOM). It's a specific verb+resource with differentiation.

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 clear usage scenarios ('Use for: extracting data not visible in accessibility snapshot...') and mentions a prerequisite (CAMOFOX_API_KEY). However, it does not explicitly state when not to use this tool or mention alternatives, but the context is sufficient.

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