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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds one genuine behavioral fact, the 'newest first' ordering, but says nothing about pagination behavior or result-capping beyond what the schema states.

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 tight sentence that front-loads the verb and resource before the scope and ordering qualifiers. Nothing is wasted and nothing is missing for its length.

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, read-only list tool with three parameters, no nested objects, and no output schema, the description covers purpose, scope, and ordering adequately. Pagination defaults are handled by the schema, so the omission is 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 description coverage is 67% (page and pageSize documented; the 'type' enum is not), placing it at the baseline where the schema carries most of the load. The description loosely maps 'played or marked as read' to the two enum values, but adds no format or behavior detail beyond the enum itself.

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 episodes') plus the qualifying scope ('the user recently played or marked as read') and the sort order ('newest first'). This clearly separates it from list_followed_episodes or search_episodes, though it doesn't name 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 phrasing 'recently played or marked as read' implies the tool's niche (personal listening history), which is useful context. However, it offers no explicit when-to-use guidance and never points to the closest alternatives (list_followed_episodes, search_episodes), leaving selection to inference.

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