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

Annotations already declare readOnlyHint and openWorldHint, so safety and openness are covered. The description adds useful context about the upstream source (iTunes Search API) and that results are normalized, but says nothing about pagination behavior or rate limits beyond what the schema implies.

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?

Short and front-loaded: purpose first, then the routing hint. The inline re-statements of Term and Country duplicate the schema and add a little clutter, but the description stays compact overall.

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 an output schema present, return values need not be explained. For a search tool with full schema coverage and annotations, the description covers what an agent needs to select and call it, though it could note pagination limits already implied by parameters.

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 all five parameters are already documented in the schema. The description merely restates Term and Country, adding no syntax or format detail beyond what the schema provides, which is the expected baseline when the schema does the heavy lifting.

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 names a specific verb and resource ('Returns normalized Apple Podcasts episodes') and pins the data source ('Apple's public iTunes Search API'). It also explicitly distinguishes itself from the show-level sibling, so an agent can route between episode and show search without opening either schema.

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 names the alternative ('Use apple_podcasts_search to search Apple Podcasts shows'), giving a clear episode-vs-show routing rule. It stops short of stating exclusions or prerequisites, but the routing signal is explicit.

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