Get recording URLs

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

Annotations already declare readOnlyHint=true; description adds behavioral context beyond that: presigned URL validity (1h/10min) and creation-time prerequisites for stream kinds. No contradiction, but doesn't mention response shape or empty-result behavior.

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?

A single, dense sentence front-loads the core purpose and packs in all essential kind distinctions without redundancy. Every clause adds 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?

Covers purpose, kinds, validity, and prerequisites adequately for a simple read-only tool with no output schema. Missing explicit return format, but annotations and purpose imply a simple list of URLs.

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 0%, so the description must compensate. It thoroughly explains the kind enum (validity, per-participant requirement) but leaves bot_id undocumented, relying on convention from sibling tools.

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+resource: 'Presigned S3 URLs for recorded media.' Clearly distinguishes from siblings like get_transcript (text) and get_bot_status (status), and enumerates the media kinds returned.

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?

Implied usage from title and purpose, but no explicit when-to-use vs alternatives. Provides kind-level prerequisites (e.g., separate_*_streams for per-participant streams), which helps choose a kind, but not tool-level selection guidance.

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