messages

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It reveals ordering ('newest last') but says nothing about how many messages are returned, whether the operation requires authentication, which chat is targeted (especially with zero parameters), or how the result is paginated.

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 ordering constraint is placed at the end for emphasis. It is appropriately sized for a zero-parameter 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?

Given zero parameters, no output schema, and no annotations, the description should at least explain how the target chat is determined (e.g., current context). It fails to do so, nor does it clarify the scope of 'recent' or how the result is used. This leaves a critical invocation gap for an agent.

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 tool has zero parameters, so the baseline score is 4 per the rubric. The description does not add parameter meaning, but there are no parameters to clarify. The implicit reliance on an unstated context ('a chat') is a minor concern but does not affect the parameter-specific score.

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 ('Show'), resource ('recent messages in a chat'), and ordering ('newest last'). However, it does not distinguish itself from sibling tools such as 'read', 'dialogs', or 'search', which likely also surface messages. The purpose is clear but not unique.

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?

Provides no guidance on when to use this tool versus alternatives like 'read' or 'search'. There is no mention of prerequisites, context, or exclusions. Only an implicit assumption that it is for viewing recent messages in a chat.

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