accept_dialog

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

The description is consistent with the readOnlyHint=false annotation, indicating mutation. However, it adds minimal behavioral context beyond accepting a dialog, such as what happens if no dialog is present or the dialog type is not a prompt.

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 extremely concise with two short sentences, each conveying essential information without any fluff. It is front-loaded and efficient.

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 one optional parameter and no output schema, the description is reasonably complete. It covers the basic action and parameter. However, it lacks error handling or prerequisite context, which would be beneficial.

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?

With 100% schema coverage, the baseline is 3. The description echoes the parameter's purpose ('Provide promptText for prompts') but adds no new meaning beyond the schema's description.

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 'Accept browser dialog' uses a specific verb and resource, clearly distinguishing it from the sibling 'dismiss_dialog'. It also clarifies the purpose for prompt dialogs with 'Provide promptText for prompts', making the tool's function unambiguous.

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 implies use for accepting dialogs, especially prompts, but provides no explicit guidance on when to use this tool versus alternatives like 'dismiss_dialog', nor does it mention prerequisites or scenarios where it should not be used.

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