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

Annotations already declare readOnly, idempotent and non-destructive, but the description adds the crucial behavioral fact that the tool performs no action and returns only a guide, plus context on why Discord's official API doesn't substitute for it. That is real disclosure beyond the structured fields, though the format of the returned guidance is only sketched ('screens, buttons, fields').

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 key behavior is front-loaded in the first two clauses, but the final sentence about Discord's official API is a long tangent that consumes roughly half the text. Phrases like 'from ChatGPT, Claude or any AI agent' add noise without informing invocation.

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?

With no input schema fields and no output schema, the description does the necessary work by explaining that the return value is a step-by-step procedure rather than message data, and by naming the follow-up tools. A slightly more concrete statement of what the returned guide contains would close the remaining gap.

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 tool takes zero parameters (schema coverage 100%), so there is nothing for the description to disambiguate; baseline 4 applies. The absence of parameters is consistent with a pure instruction-returning tool.

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 clarifies that this tool does not actually read messages but returns step-by-step instructions for doing it in Discord, which is essential given the misleading tool name 'read_channel_messages'. It also points to the cotlet_browser_* tools as the actual execution path. It stops short of distinguishing this from sibling read tools like discord_search_messages or discord_list_servers_and_channels.

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 gives a clear workflow constraint: 'opens nothing by itself' and 'then do it with the cotlet_browser_* tools', which tells the agent this is a preparatory step. However, it never states when to prefer this over discord_search_messages or other read siblings, and there are no exclusions.

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