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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and open-world nature are covered. The description adds that metadata is 'public', implying no auth requirement, but says nothing about rate limits, field shape, or the two optional include* flags beyond what the schema states.

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, zero filler; the core action is front-loaded and the sibling routing follows immediately. Every clause 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?

With an output schema covering return values and annotations covering the safety profile, the description need only establish what the tool does and how to choose it over siblings — both done. Nothing required for correct invocation is missing.

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 every parameter (including the two include* booleans) is documented in the schema itself. The description only reinforces that `uri` is the lookup key, adding little beyond the structured definition, 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?

States a specific verb ('Fetch') and resource ('public Spotify podcast-show metadata'), plus the keying parameter (`uri`). It names the three siblings it is not, so an agent can distinguish it from spotify_podcasts_show_episodes, spotify_podcasts_show_recommendations, and spotify_shows_search without opening schemas.

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?

Explicitly routes the agent: episodes go to spotify_podcasts_show_episodes, related shows/episodes to spotify_podcasts_show_recommendations, and discovery to spotify_shows_search. The condition selecting each alternative is stated rather than left to inference.

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