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

Annotations already declare readOnly/openWorld/non-destructive, so the safety profile is covered. The description adds useful context beyond annotations: the auth requirement (Cotlet API key with access to this app) and the returned fields. It doesn't discuss pagination or rate limits, but for a simple read tool this is solid.

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?

Front-loaded and mostly efficient, but the first sentence ('Podcasts in your Libsyn account with show ID, title and plan') is nearly duplicated by the second ('Returns every podcast... with its show ID, title and plan'), wasting space on redundant phrasing.

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 0-param list tool with annotations and no output schema, the description is complete enough: it covers what is returned, the auth requirement, and the downstream use of show_id. Only minor gaps (pagination behavior) remain.

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 tool takes 0 parameters, so the baseline is 4. The description nonetheless adds value by explaining how the returned show_id feeds into other tools' show_id parameter.

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+resource (list podcasts/shows in the Libsyn account) and enumerates the returned fields (show ID, title, plan). An agent can clearly distinguish this from siblings like libsyn_list_episodes or libsyn_get_show_stats.

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?

Gives strong workflow guidance: use the returned show_id as the parameter for other tools, and notes that single-show accounts default to that show. It clearly establishes this as the entry point, though it doesn't state explicit exclusions or when not to use it.

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