spotify_get_saved_shows

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

With no annotations, the description must fully disclose behavior. It only states a maximum result count of 50, omitting critical details like read-only nature, pagination, authentication needs, or output structure. The agent cannot infer safety or side effects.

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 very concise (one sentence, 9 words). It conveys the core purpose without extra words. However, it might be too brief, sacrificing necessary detail for succinctness.

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?

Given the presence of an output schema (implied by context), the description doesn't need to explain return values. However, with only one parameter and a simple purpose, the description is minimally adequate but lacks guidance on pagination or limits of the 'limit' parameter.

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 single parameter 'limit' has no schema description (0% coverage). The description mentions 'up to 50' but doesn't explain how 'limit' controls the count, its valid range, or the effect of exceeding 50. The baseline should be higher given the lack of schema descriptions.

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 states the action ('Get'), the resource ('saved/followed podcasts and shows'), and a key constraint ('up to 50'). It distinguishes this tool from siblings like spotify_check_saved_shows (which likely checks existence) and spotify_save_shows (which saves).

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?

No explicit guidance on when to use this tool versus alternatives (e.g., spotify_check_saved_shows). The description implies it's for listing but doesn't exclude other use cases or mention prerequisites. The context of use is left to the agent to infer.

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