list_channels

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

Annotations only declare readOnlyHint=true, but the description adds valuable behavioral context: admin-only auth requirement, HTTP transport, and the guarantee that tokens are never listed (with a pointer to rotate_token). This goes beyond the annotation and helps the agent understand constraints and fallback behavior.

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 with no fluff. The first sentence front-loads the key purpose and auth constraint; the second adds a critical caveat about tokens. Every word earns its place.

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 tool's simplicity (0 params, output schema present), the description covers the essential operational details: admin-only access, HTTP transport, and token behavior. The output schema handles return values, so no further explanation is needed. A slight gap is that it doesn't clarify what 'active' means, but this is minor given the overall context.

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 input schema has zero parameters, so there is nothing for the description to add. Baseline for 0 params is 4, and the description appropriately implies no parameters are needed without adding unnecessary detail.

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 the action: 'list active channels with their roles', identifying the exact verb (list), resource (channels), and scope (active, with roles). It distinguishes from siblings by explicitly noting that tokens are never listed and pointing to rotate_token for that purpose.

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 strong context: it is ADMIN ONLY and for listing channels, making the intended use case clear. It also gives an explicit exclusion for tokens ('Tokens are never listed — rotate_token issues a fresh one'), which helps route the agent away from an alternative. However, it does not explicitly compare against other listing tools like list_messages.

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