Add a podcast by its iTunes id

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

The description goes beyond the annotations by disclosing that the feed is written to a public directory, that the action cannot be undone via this API, that confirm must be true, and that write permission is required. This gives the agent a concrete understanding of impact and preconditions.

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, with the primary purpose and distinguishing condition front-loaded, followed by a compact list of caveats. Every sentence contributes meaningful information with no redundancy.

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 mutating tool with no output schema, the description covers the core operation, the required confirmation flag, permissions, irreversibility, and the public nature of the side effect. Nothing critical is missing for an agent to decide whether and how to invoke it.

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%, so the schema already documents both parameters well. The description adds context that itunes_id is the id from Apple Podcasts and that confirm must be true, but it does not need to compensate for missing schema info.

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 action ('Add a podcast to Podcast Index') and the exact input mechanism ('using its iTunes id'), which clearly distinguishes it from RSS-based submission. The mention of 'for when you have an Apple Podcasts link but not the RSS URL' further clarifies the intended resource.

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 gives the use case: when you have an Apple Podcasts link but not the RSS URL. It also points to submit_feed as the related alternative and lists the shared caveats, giving the agent clear routing and prerequisite information.

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