get_chat_messages

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

No annotations provided, so description carries full burden. It discloses return type and pagination behavior (before_message_id). Could mention it's read-only and not destructive, but operation is clearly a fetch.

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?

Front-loaded with main purpose, then concise parameter list. Docstring format is slightly verbose but remains efficient with no redundant sentences.

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 output schema exists, description appropriately focuses on input and behavior. Covers all 3 parameters, pagination, and return content (sender, text, timestamp). No gaps for a list-messages tool.

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 0%, yet description fully compensates by explaining each parameter (chat_id, limit default 50, before_message_id for pagination). Provides default values and behavior, exceeding schema information.

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?

Explicitly states 'Get messages from a specific chat,' which is a clear verb+resource combination. Distinguishes from siblings like search_messages (search across chats) and get_chat (chat info), establishing unique identity.

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?

Docstring explains parameters and pagination, implying usage when you have chat_id. Lacks explicit when-not-to-use or alternatives, but context from siblings and parameter descriptions guides selection effectively.

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