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

Despite annotations already declaring readOnly/openWorld/destructive=false, the description adds substantial behavior context they do not cover: it is free to call, typical latency is 5-10 minutes, and it enumerates the full state machine (queued, admitted, transcribed, failed) with what each implies, including that failure_refund applies on failure.

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 purpose and the polling instruction, and every sentence carries operational value. The final sentence about the episode_slug edge case is dense and slightly tangled ('for an episode we hold that it never requested, there is no request'), costing some readability.

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 correctly supplies the return semantics (the four state values and their meanings), which is exactly what is needed for a polling tool. The one gap is that both parameters are optional and the description never states the behavior when neither or both are passed.

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 coverage is 100%, so baseline is 3, but the description goes further: it explains that request_id comes from particle_podcast_request_transcription, and that episode_slug resolves your organization's request even after transcription, with an explicit edge case for episodes you never requested. It does not say what happens if both or neither key is supplied.

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 verb (read) plus the resource (the organization's transcription request) and the two lookup keys, so it is unmistakable against the sibling particle_podcast_request_transcription that creates the request.

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?

Gives explicit when-to-use and when-not-to-use guidance: it names itself as the way to wait on a request queued by particle_podcast_request_transcription, prescribes polling 'every minute or so', and explicitly says to poll 'rather than requesting again'. It also names the downstream tools to use once state is transcribed.

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