collapse_element

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

Annotations declare idempotentHint=true, and the description correctly implies a non-destructive state change with no side effects. However, the description does not explicitly confirm idempotence or clarify what happens if the element is already collapsed.

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 a single clear sentence that efficiently conveys the tool's purpose. No extraneous words, but it could be slightly enhanced with a one-word note about idempotence.

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?

Given the simple input schema, no output schema, and annotations, the description is adequate. It covers the core purpose but lacks context on prerequisites (element must be expanded) and no-failure 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 description coverage is 100%, so the baseline is 3. The description does not add details about the elementId parameter beyond what the schema provides.

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 action ('Collapse') and the resource ('expanded element') using the specific 'UIA ExpandCollapse pattern'. It differentiates from sibling tools like expand_element and toggle_element.

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 the tool is for elements that are already expanded and support the ExpandCollapse pattern, but it does not explicitly state when to use it vs. expand_element or toggle_element, nor does it exclude non-expanded elements.

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