get_libraries_by_id_episode_downloads

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

Annotations already indicate readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. However, the description adds no behavioral context beyond the endpoint—no mention of what 'episode-downloads' represents, what response to expect, or any special conditions.

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 compact and front-loaded with the core action and endpoint. There is no redundant prose, and every line contributes to identifying the tool and its parameter.

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 tool with only one parameter and an output schema, the basic invocation is clear, but the description does not explain what episode-downloads are or when to prefer this over sibling tools. This lack of semantic and comparative context makes it incomplete for reliable tool selection.

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 0%, but the description does add that 'id' is a path parameter, which the raw schema does not state. The endpoint path also implies the id refers to a library, so the single parameter is minimally explained, though not richly.

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: 'Get libraries episode-downloads' with the endpoint GET /api/libraries/{id}/episode-downloads. This makes the tool's basic function identifiable, though the phrasing is awkward and it does not explicitly distinguish itself from similar library download tools.

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 about when to use this tool versus alternatives like get_libraries_by_id_download or get_podcasts_by_id_downloads. The description only provides an endpoint and parameter, leaving the selection context entirely to the agent.

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