get_element_info

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

Annotations already declare readOnlyHint=true, so the read-only nature is established. The description adds valuable behavioral details beyond annotations: it lists what properties are returned, explains selector priority, and gives a code example. No contradiction or missing behavioral traits for a simple retrieval 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 description is five well-structured sentences: purpose, return list, usage instruction, selector priority, and a code example. Every sentence earns its place; no filler. Front-loaded with the main purpose.

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?

Despite having only 1 param and no output schema, the description is complete. It explains return values, usage context, and even includes a practical coding tip. For a tool with 67 siblings, it clearly differentiates itself and covers all necessary information for an agent to use 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 coverage is 100% (elementId is documented as 'Element ID returned by find_element'), so baseline is 3. The description reinforces the parameter's role by stating to call after find_element, but does not add new semantic details beyond the schema. Minimal added value.

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 retrieves UIA properties and selector suggestions, specifying the verb 'retrieve' and resource. It explicitly lists return values (Name, AutomationId, etc.) and differentiates from sibling tools by positioning it as the go-to after find_element for test automation.

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 explicitly says when to use: 'ALWAYS call this after find_element when generating automated test code'. It provides the context for use and explains selector reliability order, giving clear guidance on when and how to apply the tool.

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