browser_evaluate

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

No annotations; description only states core function. Running arbitrary JS can have side effects (e.g., mutations), but no disclosure. Score reflects missing behavioral warnings.

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?

Concisely one sentence, but lacks structure and depth for a potentially dangerous tool. Could be expanded without bloat.

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?

No output schema, incomplete parameter info, and complex tool (JS evaluation) needs more context (e.g., return value, scope, await behavior). Under-specified.

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?

3 params with 0% schema description coverage; description fails to explain 'ref' and 'element' roles, only mentions evaluating JS expression. Does not compensate for schema gaps.

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?

Description clearly states evaluating JavaScript expression on page or element, distinguishing it from sibling tools like browser_click or browser_navigate.

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?

No guidance on when to use this vs alternatives (e.g., InspectPage). Lacks context on prerequisites or when not to use.

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