episode_context_bundle

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

With no annotations provided, the description carries the behavioral disclosure burden. It usefully discloses the quota cost and the two underlying API calls (GET /episodes/{id} + GET /shows/{id}/episodes), which tells the agent about cost and composition. However, it does not describe error behavior, auth needs, or what the 'card' actually contains beyond the listed components.

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 compact and information-dense, covering tool output composition and quota in two short sentences. It front-loads the key purpose and adds the operational cost note without unnecessary detail.

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 description explains what data is bundled and the API cost, but there is no output schema and no mention of how response_format alters the result, what 'from_token' market behavior means, or how failures are handled. It is adequate for a simple selection decision but not fully complete for invoking the tool in varied contexts.

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%, so each parameter is already documented in the schema. The description adds no extra meaning about episode_id, market, or response_format, but it does not need to because the schema handles that burden.

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 identifies the resource (an episode), what is bundled (parent show and neighbouring episodes by release date), and the output form (one card). It distinguishes itself from simpler episode/show tools by emphasizing the contextual bundle, so an agent can tell it apart from get_episode, get_show_details, or list_show_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?

No explicit guidance is given about when to choose this tool over alternatives such as get_episode_details, get_show_details, or show_episode_timeline. The phrase 'in one card' weakly implies a bundle use case, but there is no stated when-to-use or when-not-to-use condition.

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