Game Get UI

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

Annotations provide read-only and idempotent hints. Description adds 'visible' and 'bounded' context, but does not detail more nuanced behaviors. No contradiction with annotations.

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?

Single sentence, short and direct. Could be improved by completing the truncated fragment, but no wasted words.

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?

With annotations and output schema (likely describing return format), the description covers core function. Could mention pagination or limits more explicitly.

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%, and description adds little beyond 'bounded' and 'visible'—both implicitly covered by schema (maxElements and rootPath description hints at subtree).

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?

Description clearly states verb 'Get' and resource 'bounded list of visible UI elements', which distinguishes from sibling tools like game_get_scene_tree and game_get_node_info.

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?

No guidance on when to use this tool versus alternatives, such as game_get_scene_tree or game_get_node_info. Misses opportunity to clarify use case.

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