channel_fetchMessages

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

The description discloses that messages are sorted from earliest to latest, which is a behavioral trait. However, with no annotations, it doesn't explicitly state that this is a read-only operation or mention any side effects, though 'Load' implies read.

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, front-loaded with the scope prefix, and every word earns its place. No unnecessary detail.

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?

The description is sparse, with no mention of return format, pagination, or handling of optional chatId. However, the schema covers parameters, and the tool is a simple fetch, so it's minimally complete.

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 provides 100% coverage with descriptions and examples for chatId, sessionId, and searchOptions, so the description adds no additional parameter semantics. Baseline 3 applies.

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 specific verb 'Load' with the resource 'channel messages', and the '[Channel Chat]' prefix clearly distinguishes this from sibling tools like chat_fetchMessages. It states exactly what it does.

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 '[Channel Chat]' prefix provides clear context that this tool is for channel messages, but it doesn't explicitly mention when not to use it or alternatives like chat_fetchMessages. The context is clear enough to infer usage.

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