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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds the auth requirement (`channels:read`), which is real value beyond structured fields, but says nothing about ordering, result size, or what a page contains.

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?

Three short sentences, with the core action front-loaded and the permission requirement last. The opening 'List channels' largely repeats the title, which is mild waste, but nothing else is padded.

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 simple paginated read tool with annotations covering safety, the essentials are present: scope, pagination, and auth. Missing only the return shape, which matters a bit more since there is no output schema, but the gaps are minor.

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 essentially 0% for the pagination fields (page, pageSize have no descriptions), but the description does flag that 'the list is paginated', which points the agent at those nested fields. It adds no detail on defaults, max page size, or projectId format beyond what the schema shows.

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 gives a specific verb and resource ('List channels') plus the scope ('in a project'), which clearly separates it from channels-retrieve, channels-create, and analytics-channels among the siblings. An agent can pick this out without opening the schema.

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?

It states the required permission scope (`channels:read`), which is useful context, and 'in a project' implies project-scoped listing. But it never says when to use this versus channels-retrieve or analytics-channels, and offers no exclusions or caveats.

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