Get one show from the catalog

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

Annotations already establish readOnly, idempotent, and non-destructive behavior; the description adds context beyond them by listing the returned fields and explaining that the RSS feed URL is the route to the full episode backlog. This gives the agent a clear model of what the call returns and how it connects to another tool.

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 front-loaded: it states what the tool returns, then gives the input forms, then closes with the useful next-step pointer. Every sentence earns its place with no repetition or fluff.

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 two well-documented parameters and no output schema, the description is complete: it explains what is returned, what input is accepted, and how to continue to episode data. The storefront nuance is already handled by the schema, and annotations cover the safety profile.

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?

The schema already covers both parameters at 100%, including the show id/URL formats and storefront behavior. The description's mention of an Apple id or pasted URL reinforces the schema but does not add meaningfully new parameter-level detail, so the 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 identifies the resource ('one show') and gives a specific verb frame ('Get one show from the catalog'), then enumerates exactly what the full catalog record contains. It differentiates itself from episode-level siblings like get_feed by explicitly positioning this tool as the entry point for the episode backlog.

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 states the concrete precondition for use: the caller must have an Apple id or a pasted Apple Podcasts URL. It also recommends get_feed for the episode backlog. It does not explicitly name search_podcasts or get_show_profile as alternatives, so it stops short of full when-not-to-use guidance.

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