list_my_chat_messages

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

No annotations are provided, and the description does not disclose behavioral traits such as whether pagination is zero-indexed, maximum page size, rate limits, authentication requirements, or error behaviors. It only lists parameters without explaining operational semantics.

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 concise with a clear Args list. It avoids extraneous content and front-loads the core purpose. Each sentence serves a purpose, though it could be slightly more streamlined.

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 presence of an output schema, return values are not required. However, the description lacks mention of ordering, default pagination behavior, or any edge-case handling, which are important for a listing tool with multiple optional filters.

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 description coverage is 0%, so the description must compensate. It adds useful details: 'page number', 'items per page', filter by type examples ('text', 'tool_call'), and 'ISO 8601 timestamp'. However, it does not specify default values or constraints beyond what the schema implies.

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 'List messages in a chat room', which is a verb (list) and resource (messages). It differentiates from sibling tools like 'list_agent_messages' by the 'my' prefix, but doesn't explicitly clarify that it lists the user's own chat messages.

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 vs alternatives like 'list_agent_messages' or 'list_my_chats'. No context about prerequisites or preferred scenarios.

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