xae_dialog_resolve

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

Adds substantial context beyond annotations: auto-answer rules, which prompts are destructive-class, UIA fallback behavior, refusal for unreadable buttons, and an explicit guarantee that the tool never closes the window itself. This is exactly the behavioral detail an agent needs for a destructive, non-idempotent 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?

The core action is front-loaded, and every clause carries safety or behavior information. It is slightly dense and semicolon-heavy, but not padded or redundant.

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?

Covers the difficult parts: destructive classification, auto-answer restrictions, UIA fallback, and refusal behavior. An output schema exists, so return values need not be explained, but the missing hwnd and confirm_token semantics keep it short of fully 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 description coverage is 0%, so the description must carry parameter meaning. It explains button examples and remember semantics well, but hwnd and confirm_token are not mentioned at all, leaving two of four parameters undocumented.

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?

States a specific verb and resource: clicking a button on an open XAE dialog. It is clearly distinct from the sibling xae_dialogs, which presumably lists dialogs, and the examples make the action concrete.

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?

Explains the remember=true condition and explicitly excludes machine-affecting prompts from auto-answer. It does not explicitly say to call xae_dialogs first or when to use this versus xae_dialogs, but the context is otherwise clear.

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