web_act

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

Annotations declare readOnlyHint=false and openWorldHint=true, so the general safety profile is partly covered. The description adds important session behavior ('one shot with no session'), the action repertoire, and return shape, but does not detail side effects, auth, or failure modes.

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?

Front-loads the purpose and the key alternative before listing action types. The action list is dense but necessary; overall it is appropriately sized, though it could be slightly more scannable.

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 complex browser-automation tool with no output schema, the description covers the one-shot limitation, snapshot prerequisite, action types, and return format. It omits error handling and some environment details, but the full schema and annotations cover much of the remaining context.

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 the baseline is 3 even with no parameter info in the description. The description reinforces action structure and ref workflow, but adds little meaning beyond what the schema already documents for url, actions, tier, proxy, profile, timeout, and extraction.

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?

States a specific verb and resource: opens a URL, runs actions, and returns the resulting page. It explicitly distinguishes itself from browser_open + browser_do for multi-step sessions, so an agent can tell it apart from siblings.

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?

Gives explicit when-to-use and when-not-to-use guidance: one-shot with no session, and for several steps on one login or cart use browser_open + browser_do. Also instructs taking a web_snapshot first and naming elements by ref.

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