pilot_dialog

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

Describes circular buffer behavior, clear parameter effect, return format (timestamped list) and empty case. No annotations exist, so description handles behavioral disclosure well. Minor omission: buffer size not mentioned.

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?

Concise, well-structured: purpose, usage, parameter, return, errors. Every sentence adds value; no redundancy.

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 1 parameter and no output schema, description fully covers usage, return, and edge cases. References sibling for complementary 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 covers parameter 100% with description 'Clear the buffer after reading'. Tool description repeats this with 'Set to true to clear the buffer after reading'. Adds no significant new meaning; baseline 3 applies.

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?

Clearly states it retrieves captured browser dialogs (alert, confirm, prompt) from a circular buffer. Unlike siblings like pilot_handle_dialog which configures handling, this tool retrieves past dialogs.

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 to use when viewing dialogs, checking prompt text, or verifying dialog trigger. References sibling pilot_handle_dialog for auto-handling, providing clear when-to-use guidance.

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