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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the auth requirement ('Needs the user's Cotlet API key with access to this app') and the sequencing dependency on upload completion, which is useful context. It doesn't cover rate limits or pagination, but for a single-record read with annotations, this is adequate.

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?

The description is front-loaded with what's returned, then the usage guidance and auth requirement. It's dense but not bloated; a small restatement of the track description could be trimmed slightly.

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 single-parameter read tool with annotations covering safety and no output schema, the description covers return content, sequencing, and auth. It would be a 5 if it described pagination or rate behavior, but the remaining gap is minor.

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% and the single parameter is documented there ('Recording ID from list_recordings'), so the schema does the heavy lifting. The description adds no further parameter details. 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 states a specific verb ('Returns one recording') and resource ('recording'), and details the returned structure (date, duration, participant tracks with type and upload status). An agent can distinguish this from list_recordings, download_tracks, and get_transcript at a glance.

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 explicitly names when to use it: 'Read it before download_tracks to see whether every track has finished uploading.' That's a clear ordering constraint linking it to a sibling tool with a stated selection condition.

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