get_episodes

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

Without annotations, the description carries the full burden of behavioral disclosure. It states that the tool 'Returns episode titles, numbers, and durations,' which is useful, but does not clarify that this is a read-only operation or disclose any side effects, error conditions, or permission requirements.

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 two sentences with no wasted words. The first sentence states purpose, the second provides instructions and output details. It is front-loaded and efficient.

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 that an output schema exists (not shown), the description appropriately describes return fields. It covers the essential inputs and purpose. However, it could mention potential issues like invalid rating_key or permission requirements, but for a straightforward retrieval tool, it is largely complete.

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 input schema has 0% description coverage, yet the tool description adds meaningful context: rating_key is for the show, and season_number is optional with default 0 meaning all seasons. This provides clarity beyond the schema titles alone.

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 clearly states the tool's purpose: 'Get episodes for a TV show or season.' It specifies the required input (rating_key) and optional filter (season_number), and mentions the output (episode titles, numbers, durations). This distinguishes it from siblings like get_seasons, which would handle seasons instead of episodes.

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 description provides clear instructions on how to use the tool: 'Provide the rating_key of a show. Optionally filter by season_number (0 = all seasons).' It implies usage context for retrieving episodes but does not explicitly state when not to use it or mention alternative tools like get_seasons for season-level data.

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