ringcentral_get_call_recording

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

No annotations are provided, so the description carries the burden. It clearly states the key behavioral trait (returns metadata/content URI, not audio) and includes the API endpoint. It does not mention auth requirements or response details, but for a simple read-only metadata fetch, this is sufficient.

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 concise and well-structured, with the main purpose front-loaded. The API endpoint and Args section provide useful details without verbosity, and every line earns its place.

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 tool is simple with one parameter and has an output schema. The description covers the core purpose, distinguishes it from the download sibling, and gives the source of the required parameter. This is sufficient for an agent to correctly select and invoke the tool.

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%, but the description compensates by explaining that recording_id is required and pinpointing its source: 'from a call-log entry's recording.id field'. This adds meaning beyond the bare schema type and helps the agent identify the correct value.

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 ('Get') and clearly identifies the resource ('a call recording's metadata'). It also distinguishes itself from the sibling tool `ringcentral_download_call_recording` by stating it returns a content URI, not the audio itself.

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 gives clear context on what the tool does and where the recording_id comes from, but it does not explicitly name the alternative tool or state when not to use it. However, the sibling list and the parenthetical '(returns a content URI, not the audio itself)' imply when to prefer the download tool.

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