mattermost_get_channel_history

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

No annotations are provided, so the description carries full burden. It mentions that by default all messages are returned and that limit restricts count. However, it does not disclose ordering, whether messages include deleted ones, or any rate limits or auth requirements. For a read operation, this is minimally adequate but lacks richer behavioral context.

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 sentences: the first states the core purpose, and the second clarifies default behavior and the limit parameter. Every word is functional, with no redundancy or filler.

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 7 parameters and no output schema, the description is somewhat sparse. It does not explain pagination behavior (page only used when limit>0 is in schema but not highlighted), nor the maximum results or ordering. It covers the basics but lacks completeness for advanced query scenarios.

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 covers 100% of parameters with descriptions. The description adds value by explaining the default for limit ('returns ALL messages') and how to use since_date/before_date for date ranges. This reinforces usage tips beyond what the schema provides.

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 uses the verb 'Get' with the resource 'messages from a Mattermost channel.' It clearly states the default behavior (all messages) and mentions the limit parameter. Sibling tools like `mattermost_post_message` and `mattermost_get_thread_replies` are distinct, so there is no ambiguity.

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 implies usage for retrieving messages but does not explicitly state when to use this tool compared to alternatives like `mattermost_get_thread_replies` for thread replies. No exclusion criteria or conditions are provided, so guidance is implied but not explicit.

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