ringcentral_download_call_recording

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

With no annotations, the description carries the transparency burden. It clearly discloses that the output is metadata, not the raw binary, and notes the media.ringcentral.com host difference. This is a significant behavioral trait beyond the tool name. It doesn't cover error handling or auth, but for a simple metadata fetch, the key gotcha is addressed.

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 brief, well-structured, and front-loaded with the essential behavior. The API endpoint and argument description are clearly separated, and every sentence adds value. No wasted words.

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?

The output schema exists, so return values need not be fully described. The description provides the key limitation (metadata not bytes), the API host, and the source of the recording ID. It lacks error-handling notes, but given the presence of an output schema and the simplicity of the tool, this is sufficient.

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?

The only parameter, recording_id, is fully explained: it is required and must come from a call-log entry's `recording.id` field. This adds meaning beyond the schema, which only defines it as a string. Since schema coverage is 0%, the description compensates completely.

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 uses a specific verb ('Download') and resource ('call recording's media content'), then immediately clarifies the actual behavior: it returns metadata about the binary (content type and size), not raw audio bytes. This distinguishes it from siblings like ringcentral_get_call_recording, which likely returns other recording details.

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?

The description implicitly explains when to use this tool: when you need content type and size, not the actual audio bytes (which aren't representable). It doesn't explicitly name alternatives, but the context and contrast with raw audio bytes gives clear usage context, and the API endpoint provides additional integration guidance.

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