user_messages

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

With no annotations, the description carries the full burden of behavioral disclosure. 'Return' suggests a read-only operation and 'current ... shown in active test-client window' scopes what is read, but it does not disclose whether the messages panel must be open, whether messages are cleared or refreshed, or any other relevant behavior.

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, front-loaded sentence with no filler or repetition. Every word contributes meaning, and it is appropriately compact for a simple read tool.

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?

The tool is relatively simple, with one optional parameter and no output schema, but the description still leaves some gaps. It does not clarify the return structure, the role of session_id, or any prerequisites such as an open messages panel. It is adequate for basic invocation but not fully complete.

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 schema has one parameter, session_id, with 0% description coverage in the schema, and the description does not mention it at all. The parameter is optional and has a default, which reduces the risk, but an agent receives no help understanding what session_id refers to or how it affects the returned messages.

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 a specific action ('Return') and resource ('current user messages shown in the active test-client window'). It is distinct from sibling tools like close_user_messages_panel because it is a read operation rather than a panel control action, though it does not explicitly name that sibling.

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 when to use the tool: whenever the current user messages displayed in the active test-client window are needed. However, it gives no explicit guidance about when not to use it or what alternatives exist, leaving usage somewhat inferred.

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