get_episode

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

With no annotations, the description carries the burden. It discloses the HTTP method and parameter placement, but doesn't mention read-only nature (obvious from GET), error behavior, or pagination defaults. It adds a hint about query usage but is otherwise minimal.

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, front-loaded with purpose and endpoint, then parameter placement. No redundant words or repetition of schema (which is empty).

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?

The output schema exists, so return format is covered. However, the description doesn't mention required parameters, auth, or failure cases. For a simple GET, it's adequate but could state that path_params must include an episodeId.

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%, so the description must compensate. It explains the role of path_params (route IDs) and query (filtering, pagination, sorting, include), but doesn't enumerate specific fields or formats. This is basic guidance but not exhaustive.

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 'Get training episode details' – a specific verb and resource – and specifies the exact endpoint `GET /episodes/{episodeId}`, distinguishing it from list_episodes. The agent can immediately understand this fetches a single episode by ID.

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?

Provides explicit guidance on where to place inputs: route IDs in path_params and filtering/pagination/sorting/include in query. This is actionable, though it doesn't explicitly state when to choose this over list_episodes; the distinction is implied by 'details' and the endpoint.

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