pilot_handle_dialog

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

With no annotations, the description explains it is a configuration-only call that always succeeds, captures dialog messages in buffer, and default behavior for prompt_text. Sufficient for a read-like configuration tool.

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?

Four well-organized sentences covering purpose, usage, parameters, return, and errors with no redundancy or fluff.

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 2-parameter configuration tool with no output schema and no annotations, the description covers all needed aspects: purpose, usage, parameter details, return, and error behavior.

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%, but description adds value by clarifying prompt_text defaults to empty string when omitted and the effect of accept boolean on all dialog types.

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 configures automatic handling of native browser dialogs (alert, confirm, prompt) that block page interaction, using strong verb 'configure' and distinguishing it from sibling pilot_dialog which captures messages.

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 says 'Use when the user wants to pre-configure dialog behavior...' and references pilot_dialog for message capture, providing clear context and differentiation, though no explicit 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.