list_episodes

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

No annotations are provided, so the description carries full responsibility for disclosing behavior. It only states 'List all episodes' without mentioning the response format (e.g., titles only or full details), ordering, pagination, error conditions, or any side effects. This is a minimal statement that leaves the agent uncertain about what to expect.

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 a single, front-loaded sentence with no unnecessary words. It efficiently communicates the core purpose without padding.

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 simple list tool with well-documented parameters, the description is minimally adequate. However, without an output schema or annotations, it would benefit from specifying what the list contains (e.g., episode titles, air dates) to fully prepare the agent. The description is not misleading but lacks these details.

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 100%: both 'series' and 'season' have descriptive text. The tool description adds no new information about the parameters beyond what the schema already offers, so the baseline score of 3 is appropriate.

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 uses the specific verb 'List' with a clear resource ('all episodes for a Star Trek series season'). It directly distinguishes itself from sibling tool 'get_episode' (which presumably retrieves a single episode) by specifying 'all episodes' and the scope of a season.

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 implies when to use the tool (when you need a complete list of episodes for a given season), but it does not explicitly state alternatives or exclusions. For example, it does not mention that 'get_episode' should be used for a single episode or that 'search_memory_alpha' may be better for textual queries.

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