op3_get_show

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

Annotations already mark this as read-only, idempotent, and non-destructive. The description adds useful behavioral context beyond that: include_episodes is off by default due to potentially hundreds of episodes, and episode IDs obtained here are the basis for downstream episode tools. No contradiction with annotations.

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, each earning its place: the main purpose, the optional behavior with rationale, and the downstream usage of returned IDs. It is front-loaded and free of filler.

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 read-only lookup with three well-described parameters, the description is complete. It covers what data is returned, the optional episode expansion, and how the results connect to other tools. No output schema exists, but the listed return fields are sufficient for the agent.

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 the parameters are already well documented. The description reinforces the purpose of include_episodes and the role of episode IDs but does not add significant semantic detail beyond what the schema already provides. Baseline 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 clearly states the action ('Look up a show on OP3') and the resource, listing the returned fields (uuid, title, podcast guid, public stats page) and the optional episode list. It does not explicitly distinguish this tool from siblings like op3_resolve_show, but the core purpose is specific and understandable.

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 gives clear context: use this tool to look up a show and optionally retrieve episode IDs, and notes that these episode IDs are what episode-level tools filter on. It does not explicitly name alternatives or say when not to use it, but the context is enough for an agent to know when it is relevant.

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