list_messages

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions retrieval and pagination parameters (before_id, since_id, after_id, limit) but doesn't cover critical aspects like rate limits, authentication needs, error conditions, or what happens with invalid IDs. For a read operation with multiple parameters, this leaves significant gaps in understanding the tool's 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 efficiently structured with a clear purpose statement followed by a bullet-point style explanation of each parameter. Every sentence earns its place by providing essential information without redundancy. The formatting makes it easy to scan and understand quickly.

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 the tool's moderate complexity (5 parameters, no annotations, no output schema), the description is partially complete. It excels at parameter semantics but lacks behavioral context and usage guidelines. For a retrieval tool with pagination, it should ideally mention ordering, response format, or error handling to be 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 description adds substantial value beyond the input schema, which has 0% description coverage. It explains each parameter's purpose: group_id identifies the group, before_id/since_id/after_id control pagination timing, and limit specifies quantity with max/default values. This compensates fully for the schema's lack of descriptions, making parameter meanings clear.

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 verb 'retrieve' and resource 'messages from a group', making the purpose unambiguous. It distinguishes from siblings like 'send_message' or 'list_direct_messages' by focusing on retrieval from groups. However, it doesn't explicitly differentiate from 'list_chats' or 'list_direct_messages' beyond the group context.

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 provides no guidance on when to use this tool versus alternatives like 'list_chats', 'list_direct_messages', or 'get_group' for group information. It mentions the tool's function but offers no context about appropriate scenarios or exclusions, leaving the agent to infer usage from the name and parameters alone.

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