get_libraries_by_id_recent_episodes

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

The annotations already cover the safety profile (read-only, idempotent, non-destructive), so the description is not required to restate that. It adds the exact HTTP method and route, but no additional behavioral context such as pagination, ordering, or response semantics; this is adequate but not rich.

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 description is short and front-loads the core action and exact route; no wasted prose. It is slightly terse, but for a one-parameter read-only call the brevity is appropriate.

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?

Given the low complexity, the annotations, and the presence of an output schema, the description is minimally viable for making the call. However, it lacks any indication of when the recent-episodes endpoint is appropriate, what filtering or pagination exists, and what distinguishes it from adjacent library endpoints.

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?

With 0% schema description coverage, the description carries the burden of explaining the parameter. It only repeats that id is a path parameter, which the endpoint path already implies, and doesn't clarify that id identifies a library or how to obtain it. This is thin compensation for the schema 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 names a specific verb ('Get') and resource ('libraries recent-episodes'), and the explicit endpoint GET /api/libraries/{id}/recent-episodes makes the operation unmistakable. It doesn't elaborate on what a recent-episode is, but the resource is clear enough to separate it from most siblings.

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?

There is no guidance on when to use this tool versus alternatives such as get_libraries_by_id_episode_downloads or get_libraries_by_id_items. The description only states the endpoint and provides no context, exclusions, or selection criteria.

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