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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint false and closed-world scope, so the safety profile is covered. The description adds only the clarification of what content types a collection contains; it says nothing about recency window, ordering, or truncation behavior that an agent might need beyond the annotations.

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?

A single front-loaded sentence with no filler; the parenthetical content-type list is short and genuinely disambiguating. It is efficient, though it leaves no room for scoping detail.

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?

The tool is simple, the parameter is fully documented, and an output schema exists, so return format needn't be described. Still, an agent gets no hint about the recency window, ordering, or how results relate to search_collections, which is a modest gap for a list tool.

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?

Only one optional parameter, and the schema documents it fully (default 10, max 50) at 100% coverage, so the schema does the heavy lifting. The description adds no meaning about limit, so baseline 3 applies.

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?

States a specific verb and resource ('List the user's most recently added collections') and clarifies what a collection holds (books, articles, podcasts). This separates it from get_collection and search_collections, though it never names those siblings explicitly.

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 word 'recent' implies a browsing/recency use case rather than a lookup, which implicitly contrasts with search_collections and get_collection, but no explicit when-to-use or when-not-to-use guidance is given and no sibling is named.

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