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

Annotations already declare readOnlyHint and destructiveHint=false, so safety is covered; the description still adds value by disclosing the UUID ordering and that the call does not advance seen positions, which is not derivable from the annotations. It stops short of describing result shape or paging side effects.

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, front-loaded with the usage trigger before the return behavior and the edge-case instruction. No filler, though the 'Does not modify Lists' clause partially repeats the readOnly annotation.

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 no-required-parameter read-only listing with no output schema, the description covers the trigger, return contents, ordering, and the empty-List case. It leaves the after_id pagination contract entirely to the schema and says nothing about error or auth conditions, so it is adequate but not fully complete.

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 description coverage is only 50% – limit is well documented in the schema, but after_id has nothing beyond a UUID pattern. The description never mentions either parameter; its 'ordered by UUID' phrase hints at after_id's format but does not explain how to use it, so it fails to compensate for the coverage gap.

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 states a specific verb and resource: it returns the connected account's saved List directory, ordered by UUID. That is clear enough to separate it from a single-List tool, though it never names the sibling (get_list) an agent should use for a specific List.

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 one when-to-use trigger (researching followed coins/Crypto Voices) and a fallback instruction when no List exists (ask for named interests). However it offers no routing to alternatives such as get_list or query_list_activity, so the usage guidance is implied rather than explicit.

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