Publish podcast corpus

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

Annotations declare destructiveHint=true and idempotentHint=true; the description earns credit by explaining exactly what is destroyed ('replaces the prior corpus/index snapshot'), that partial attempts are repaired, and that missing audio/transcript prerequisites return an error. This is substantive context beyond the structured fields and is consistent with them.

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?

Four tight sentences, front-loaded with the core action and followed by sequencing, side-effects, and error/success behavior. Every sentence adds distinct value.

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 no output schema, the description compensates by noting that success identifies the published item and failures return an error on missing prerequisites. Combined with the annotations, an agent has everything needed to invoke it correctly.

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?

There is a single parameter with 100% schema description coverage (the schema already clarifies it is the integer episode ID, not the feed ID). The description adds no further parameter semantics, so the baseline 3 applies since the schema carries the meaning.

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?

Specific verb (Publish) plus resource (completed podcast transcript into a searchable local corpus with source-aware citations). It clearly distinguishes itself from the ingestion siblings by naming transcribe_podcast_episode and download_podcast_episode as adjacent steps.

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?

Explicit when-to-use is given: 'Use after transcribe_podcast_episode completes', with the audio-acquisition alternative named ('use download_podcast_episode'). Prerequisites and their failure mode are also stated, so the agent knows the sequencing and entry condition.

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