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

Annotations already establish readOnly, non-destructive and open-world behavior, and the description adds real context on top: the result is inline text with no file to download or parse, the call is gated on a 'done' status, and the transcript of a long episode produces a large payload. That size warning is exactly the kind of cost/behavior hint annotations cannot convey.

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?

Three short sentences, each carrying distinct information: what is returned, the availability gate, and the include/size caveat. The opening sentence is slightly front-loaded with content nouns before the framing, but there is no filler.

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 must describe the return, and it does so by enumerating the three content sections and their text form. The only gap is behavior when the order is not yet 'done' or the episode was never edited, which is left implicit.

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 order_id, api_key and include are already documented, including the comma-separated enum of summary/show_notes/transcript. The description restates that include limits the answer to the named parts but adds no format or default detail beyond the schema, so the baseline 3 applies.

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?

The description names the exact resources returned – show notes, full transcript with speaker labels, and edit summary – for an edited podcast episode, and frames them as inline text rather than a downloadable file. That is specific enough to separate it from siblings like barevalue_status or barevalue_list_orders, though it never states an explicit retrieval verb.

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?

It gives a concrete precondition – 'Available once barevalue_status reports "done"' – which tells the agent when the call is valid. It does not name an alternative tool or state what to do if the episode is not yet done, so the routing guidance is clear but not exhaustive.

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