Sa Menu

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

No annotations are provided, so the description carries the full disclosure burden. It hints at output content ('values, options, risk') but says nothing about side effects of opening a menu or the 'Switch to this mode first' behavior, reversibility, or permissions. Substantial behavioral gaps remain.

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?

A single front-loaded sentence with no wasted words. The action and its return are stated immediately.

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 no output schema and no annotations, the description partially compensates by naming the returned control data, but for a 4-parameter interaction tool it omits side-effect and mode-switching behavior, leaving the agent under-informed on how opening a menu affects application state.

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 75% with inline descriptions for menu, mode, and page, so the schema does most of the work; 'screenshot' lacks a description. The tool description itself adds no parameter meaning beyond what the schema already states, so the baseline 3 applies.

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+resource ('Open a right-hand menu') and what it returns ('live controls'), so the purpose is legible. However, it does not distinguish itself from close siblings like sa_controls or sa_dialog, which also deal with menus/controls, leaving some ambiguity about when this tool versus those apply.

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?

There is no explicit when-to-use, when-not-to-use, or alternative routing. The phrase 'right-hand menu' implies context, but an agent gets no guidance on how this differs from sa_controls, sa_dialog, sa_gui, or sa_press.

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