Look up a show on OP3

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds useful context the annotations lack: that include_episodes is off by default because long-running shows return hundreds of episodes, i.e. a payload-size warning, plus the id-chaining contract for episode-level tools.

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?

Three sentences, front-loaded with the core lookup, then the optional expansion, then the downstream chaining note. Every sentence carries information, though the include_episodes clause partially repeats the schema's own description of that flag.

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?

With no output schema, the description compensates by naming the returned fields (uuid, title, podcast guid, stats page) and the shape of the episode list (ids, titles, publication dates). It is nearly complete for a lookup tool; only the form of the 'public stats page' value is left implicit.

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 identifier, episode_limit and include_episodes are already fully documented in the schema. The description only restates the include_episodes behavior ('also get the episode list'), adding no syntax or format detail beyond what the schema provides. Baseline 3 applies.

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 gives a specific verb (look up) and resource (a show) and enumerates what comes back: uuid, title, podcast guid and public stats page. That is well beyond a restatement of the name. It does not explicitly distinguish itself from the sibling op3_resolve_show, which is the one nearby tool an agent could confuse it with.

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?

It tells the agent to set include_episodes when the episode list is needed, and states that 'Episode ids from here are what the episode-level tools filter on' – a genuine routing hint toward the episode-level siblings. It does not say when to prefer op3_resolve_show or op3_list_episodes instead, so the guidance is clear but not exhaustive.

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