ui_expand

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

The description discloses that it uses ExpandCollapsePattern, that it's safe to call on already-expanded elements, and the return format. However, it does not specify if the element must be visible or enabled, or any other side effects. Annotations are minimal (only openWorldHint), so description carries burden but has gaps.

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 concise: one sentence for purpose, one for safety and return, and a clear Args section. Every sentence adds value, and it is front-loaded with the core action.

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 parameter and no output schema, the description covers the operation, safety, and return format. It provides enough context for an agent to use it correctly. Minor missing details (e.g., visibility requirements) are not critical given its simplicity.

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?

The only parameter, automation_id, is described as 'AutomationId of the element to expand.' This adds meaning beyond the schema (which only provides title and type), but given the schema coverage is 0%, the description provides necessary context. Adequate but not exceptional.

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's purpose: expand a TreeView node, ComboBox dropdown, or other collapsible element. It uses a specific verb and resource, and distinguishes from siblings like ui_collapse and ui_toggle.

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 mentions that expanding an already-expanded element is safe, but does not explicitly state when to use this tool over alternatives like ui_toggle or ui_invoke. No contraindications or usage context beyond that.

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