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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is low; the description adds data-scope behavior beyond them by disclosing that archived read-only rooms are included and that no reconnect is needed for the call. It does not cover pagination or result shape, but adds genuine 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?

Information-dense and front-loaded, leading with what is listed before describing routing to pages_list. Four compact sentences with little waste, though the parameter mentions are slightly scattered.

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?

For a read-only listing tool with no output schema and one param, the description covers scope, included archived data, and follow-on tooling. Return format/pagination are absent but are not strictly required given no output schema.

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 100% for the single 'connection' parameter, giving a baseline of 3. However, the description references 'room_id' and 'private' as if they were inputs to this tool, while the input schema contains neither, creating a mismatch between described and actual parameters.

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?

States a specific verb and resource ('List channels') plus scope ('joined rooms and your private memory vault', including archived read-only rooms). This is clearly distinguishable in intent from rooms_list, though it doesn't explicitly name the sibling it contrasts with.

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?

Provides downstream guidance: 'Send and search using the chosen channel_id; use pages_list(channel_id) to discover its shared pages,' which routes the agent to the right next tool. It lacks explicit when-not conditions, but the context for use is clear.

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