get_library_sections_by_section_id_episodes

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

Annotations already disclose readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false. The description adds no behavioral context beyond restating the HTTP verb and path; it does not explain pagination, response shape, or any side effects or limitations. It neither conflicts with annotations nor enriches them meaningfully.

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, front-loaded with the core purpose, and contains no fluff. The endpoint and argument are stated directly. While it could be more informative, every present line earns its place.

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?

With a single required parameter, an output schema, and read-only annotations, the description is minimally sufficient for a simple fetch. However, it lacks any context about what episodes are, what kind of section is valid, or how this differs from the many closely related section endpoints in the sibling list.

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?

The only parameter, section_id, has a schema title 'Section Id', and the description says 'The id of the section', which is essentially a restatement of the schema with no additional meaning. It does not explain what a section is, how to find a valid section ID, or any constraints beyond being an integer.

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 clear verb and resource: 'Get Section Episodes' and gives the exact endpoint path 'GET /library/sections/{sectionId}/episodes'. It is unambiguous about what the tool does, but it does not differentiate it from the many sibling section endpoints like shows, movies, or albums.

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?

No guidance is provided about when to use this tool versus alternatives. It does not mention that this is for TV episode content in a library section, nor does it exclude sibling tools such as get_library_sections_by_section_id_shows or get_library_sections_by_section_id_movies. An agent must infer usage entirely from the name.

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