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

Annotations declare non-read-only and open-world, and the description adds real substance beyond them: the action is immediate and fans out to all connected destinations, listeners see it once their apps refresh, confirmation is on by default and can be switched off, and the user's Cotlet API key with app access is required. That is a rich behavioral profile for a mutation tool.

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 action, but the first two sentences are near-duplicates ('Publish a draft now to every destination your show is connected to' vs 'Publishes a draft at once to every destination the show is connected to'), which wastes a sentence without adding information.

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?

Covers purpose, immediate effect, user-visible consequence, the alternative tool, confirmation behavior, and auth requirements, which is ample for a single-parameter mutation with no output schema. Return details are omitted but no output schema exists to warrant them.

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?

Only one parameter (episode_id) and the schema description is 100% covered ('Episode ID from list_episodes'). The description adds nothing about the parameter's format or constraints, so this is the baseline case where the schema does all the work.

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?

Names a specific verb (publish), the object (a draft episode), and the scope (every destination the show is connected to), and explicitly contrasts with the sibling schedule_episode. An agent can distinguish this from create_episode or schedule_episode without opening any schema.

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?

States the key routing rule explicitly: 'To release later, use schedule_episode,' which tells the agent when to pick the alternative. It also gives a confirmation policy ('confirm with the user before each call'). It does not mention prerequisites like needing an existing draft, but the core alternative is clearly named.

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