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

Annotations already cover read-only, idempotent and non-destructive, so the description's added value is the ordering guarantee ('oldest message first'), the content inventory, and the cost note ('Free'), which is genuinely useful for deciding whether to fetch. Pagination behavior is left to the schema rather than described, keeping it from a 5.

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?

What it returns is front-loaded, followed by the use case, the identification options, and a one-word cost note. Every sentence carries distinct information and there is no filler.

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 single-resource fetch with no output schema, the description covers what is returned, in what order, how to identify the target, and the cost. Nothing an agent needs in order to call it correctly is missing.

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%, so the baseline would be 3; the description earns an extra point by explaining the two key identifiers semantically — chat_id comes from list_chats, list_id from run_ugc_agent — which clarifies that they are alternative ways to target the same chat. It says nothing about limit/cursor, which the schema already handles.

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 names a specific verb and resource ('Read one of the user's chats') and enumerates exactly what comes back: requests, agent answers, step summaries, run progress and the result table id. It is clearly distinguishable from siblings like list_chats (enumeration) and delete_chat/rename_chat (mutation).

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 concrete use case ('recall what was asked and found earlier') and tells the agent how to obtain the two identifiers, pointing at list_chats and run_ugc_agent. It does not state an explicit when-not-to-use or name an alternative retrieval tool, so it falls short of a 5.

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