click_and_snapshot

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

With no annotations provided, the description carries the behavioral disclosure burden. It transparently describes the sequence: click, wait, then return a snapshot. It also signals the likely side effect that clicks may trigger navigation or dialogs. It does not detail failure behavior or edge cases, but the core behavior is clearly disclosed.

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?

The description is a single, well-structured sentence that front-loads the operational behavior and then adds the target use case. There is no filler or redundant content.

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 tool with two parameters, full schema coverage, and no output schema, the description is sufficiently complete. It explains the operation, the return value ('snapshot'), and the intended scenario. Nothing essential is missing for an agent to decide when and how to call it.

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 schema already documents both parameters. The description reinforces that 'ref' is used for clicking and 'wait' happens before snapshot, but it does not add significant new meaning beyond the schema's own parameter descriptions.

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 states a specific compound action: 'Click element by ref + wait + return snapshot.' It clearly identifies the resource (element by ref), the action (click), and the follow-up behavior (wait and snapshot). It also distinguishes itself from sibling click tools by mentioning the snapshot return and the navigation/dialog context.

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 context: 'Perfect for buttons that trigger navigation/dialog.' This tells the agent when the tool is appropriate. However, it does not explicitly mention when not to use it or name alternatives like click_and_wait or browser_snapshot.

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