add_podcast_from_feed

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

Annotations already declare non-read-only, non-destructive, idempotent behavior, and the description adds the non-obvious mechanism that the server performs the feed fetch server-side as part of ingestion. It does not describe failure/dedup behavior if the same feed is added twice, but for an annotation-covered create operation this is solid added context.

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 with the core action, followed by one short clarifying analogy and a tidy Args list — no filler. The 'Unlike a book' sentence is slightly chatty but earns its place by preventing the wrong tool choice (file upload).

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 and annotations present, the description only needed to cover mechanism and parameters, and it does: feed fetching, library typing, and all four args including the auto_download toggle. Missing only edge-case behavior (duplicate feeds, fetch failure), which is minor here.

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 0%, so the description carries the full parameter burden and does it: library_id (podcast-type library, sourced from list_libraries), folder_id (folder within that library), feed_url (RSS feed URL), and auto_download (keep downloading new episodes). Types, the default of false, and valid ID formats are left to the schema.

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?

Clear verb+resource: 'Add a podcast by RSS feed', with the key differentiator that the server fetches the feed itself rather than requiring an uploaded file. It implicitly contrasts with book-upload tools ('Unlike a book, a podcast needs no local file'), though it does not distinguish itself from the similarly-named sibling create_podcasts_feed.

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?

Sets the context for use (podcast ingestion, no local file needed) and routes the agent for a required prerequisite by noting library_id must be a podcast-type library 'from list_libraries'. It lacks an explicit when-not or a direct pointer to the alternative (e.g., upload_book / create_podcasts_feed).

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