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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety profile for a catalog search. The description adds only that results contain titles, show references and IDs, which is partly redundant given an output schema exists, and says nothing about pagination, rate limits, or clamping behavior.

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 tight sentences that are front-loaded with the search action and then the result/follow-up contract. Every clause carries information; nothing is padded.

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?

An output schema exists, so leaving return-shape detail to it is fine, and the annotations cover safety. Still, for an 11-parameter tool the description is thin: it never explains the optional include* toggles or the required-term caveat, leaving gaps an agent would have to reconcile from the schema alone.

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% (all 11 params documented, including clamps and defaults), so the baseline of 3 applies. The description adds no parameter meaning beyond the schema, and notably does not resolve the tension that searchTerm is labelled required in-schema but the tool reports zero required parameters.

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 states a specific verb (Search), resource (Spotify podcast episodes) and mechanism (by keyword), and mentions a downstream detail/chapter fetch. It is clearly a podcast-episode search, though it does not explicitly name the sibling it differs from (e.g. spotify_podcasts_search or apple_podcasts_episodes_search).

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?

Usage is implied by 'by keyword', and the description describes a follow-up flow (reuse the returned episode ID for detail/chapter). However, it offers no when-to-use vs when-not guidance or naming of alternative search tools, so the caller must infer selection criteria.

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