get_episodes

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

Description reveals that failures are captured per item, a non-obvious behavioral trait. However, with no annotations, it does not disclose read-only status, rate limits, or other safety aspects. Adequate but not comprehensive.

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?

Two sentences, no wasted words, front-loaded with action. Efficient and easy to digest.

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?

Lacks essential information for a batch operation: input format (what the strings should be), authentication requirements, output schema details, and any limits on the number of inputs. Incomplete for effective use.

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 coverage is 0%, and description fails to explain the single parameter 'values'. It does not specify what the strings represent (e.g., episode IDs, URLs), leaving the agent to guess.

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?

Description clearly states 'Fetch many episodes at once', specifying verb and resource. The phrase 'one ordered result per input, failures captured per item' distinguishes this batch operation from the single-episode sibling tool 'get_episode'.

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?

Implies batch usage, but no explicit guidance on when to use this tool versus the singular 'get_episode'. No mention of when not to use or alternative tools.

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