dialog_auto_handle

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 covers persistence across tabs, one-shot versus persistent semantics, fire-time reading of the action, and removal behavior. This is unusually transparent for an install-style 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?

Three tight sentences with no wasted words. The most important distinguishing fact ('PERSISTENT') is front-loaded, and each sentence adds a distinct piece of information: persistence scope, dynamic action reads, and removal.

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 three simple parameters and no output schema, the description plus input schema fully covers how to install, configure, and remove the handler. There are no significant gaps that would prevent an agent from using it correctly.

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 only 33%, but the description adds meaningful semantics for enabled ('set enabled=false to remove it') and action ('reads its action at fire time'). The prompt_text parameter is already documented in the schema, though the description does not explain its interaction with the action parameter.

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 opens with a specific verb ('Install') and resource ('PERSISTENT dialog handler'), then immediately distinguishes it from the one-shot sibling dialog_handle. The scope ('every dialog and every tab') makes its purpose unmistakable.

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?

It explicitly contrasts with dialog_handle ('dialog_handle is one-shot') and explains when this persistent variant is appropriate. It also states exactly how to remove the handler with enabled=false, giving clear lifecycle guidance.

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