handle_dialog

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states this is a setup operation but does not disclose what happens if called multiple times, whether it modifies session state, or any side effects. Missing details on behavior beyond the setup action.

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 sentences with zero wasted words. The most critical information (ordering requirement) is front-loaded. Every sentence adds value.

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 simple tool with 3 parameters, no output schema, and no annotations, the description covers purpose and ordering but lacks behavioral context (e.g., return value, error cases, effect on session). It is adequate but could be more 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 coverage is 100%, so the schema already describes all parameters. The description adds minimal value: it repeats the optional nature of 'prompt_text' (already in schema). No additional semantics for 'action' or 'session_id' beyond what the enum and description provide.

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 verb 'Set up', the resource 'JavaScript dialogs (alert, confirm, prompt)', and the scope 'on a session'. It is specific and distinguishes this tool from siblings like 'click_element' or 'navigate_session' that handle different browser interactions.

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?

Explicitly states the critical ordering requirement: 'Must be called BEFORE the action that triggers the dialog.' This provides clear when-to-use guidance. No alternatives are mentioned, but no sibling tool serves the same purpose.

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