get-messages

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

No annotations provided, so description must cover behavioral traits. It correctly implies a read-only operation and mentions return type ('array of messages with basic details'), but does not disclose potential side effects, authentication needs, or error handling.

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?

Two concise sentences with front-loaded key information ('BULK RETRIEVAL'). Minor waste from emoji and capitalization, but overall efficient.

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?

No output schema, so description should explain return values; 'array of messages with basic details' is vague. Parameters are well-covered in schema, but lack of specifics on 'basic details' is a gap.

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?

Input schema has 100% coverage with descriptions for all 5 parameters. The description adds no additional meaning beyond summarizing the existing schema fields (filtering, pagination, search).

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 'Get multiple messages' with verbs 'get' and resource 'messages'. It distinguishes from siblings like get-message (singular) and search-users by explicitly mentioning bulk retrieval and filtering capabilities.

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 usage context: 'browse conversations, search for content, or get message history.' However, it lacks explicit guidance on when not to use this tool compared to alternatives like get-message or search-users.

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