chat_fetchMessages

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

The only disclosed behavior is sorting order (earliest to latest). The description omits key details such as whether chatId is optional, what searchOptions controls, pagination behavior, and the return value structure. With no annotations, this is insufficient disclosure for a data-loading tool.

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 two short sentences with no filler. It front-loads the purpose ('Load chat messages') and adds the ordering detail, making it highly efficient with zero waste.

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 optional chatId, the nested searchOptions object, and the absence of output schema and annotations, this brief description is inadequate for an agent to reliably invoke the tool. It fails to explain how chatId is used, what the response looks like, or how searchOptions affects results.

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 schema already describes all three parameters with examples and a coverage of 100%. The description adds no additional parameter context, so the baseline of 3 is appropriate. It does not clarify the optionality of chatId, but the schema itself is self-documenting.

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 'Load chat messages' which identifies the action and resource. The '[Chat]' prefix helps distinguish it from channel_fetchMessages, and the sorting note adds specificity. However, it does not explicitly differentiate from client_searchMessages, so it is not a 5.

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?

No guidance is provided on when to use this tool versus alternatives like client_searchMessages or channel_fetchMessages. The description lacks context about prerequisites (e.g., whether chatId is needed) or exclusions, leaving the agent without clear selection criteria.

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