Turn an Apple Podcasts link into ids

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint: false, so no contradiction exists. The description adds useful behavioral context beyond annotations: the episode id is optional, the storefront is returned, and Apple share URLs hide the episode id in a query parameter. This helps set expectations without overpromising.

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, no filler. The first sentence states the action and outputs; the second explains why this tool exists relative to the rest of the API. Every sentence earns its place.

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 single-parameter, read-only resolver with no output schema, the description is complete enough. It covers the input, the various return values, the optional nature of the episode id, and the storefront, and gives enough rationale for an agent to know when to call it. No critical missing context for correct invocation.

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%, and the input schema already documents that 'url' may be an Apple Podcasts URL or a bare numeric id that passes through. The description reinforces the URL-to-id bridge but adds little parameter-level detail beyond what the schema provides, so the baseline 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 a specific verb ('Take ... and return') and clearly names the resource (an Apple Podcasts URL) and the outputs (show id, episode id, storefront). It also distinguishes this tool from every sibling by noting that all other tools are keyed by id, making its unique role unmistakable.

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 clearly states when to use the tool: when someone pastes an Apple Podcasts URL, and explains why this step is needed before using the id-keyed sibling tools. It does not name specific alternatives or exclusions, but the context is strong enough that an agent would know this is the bridge for link-to-id conversion.

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