get_recording

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

Annotations are absent, so the description must carry the behavioral burden. It implies a read-only operation ('get a link') but does not disclose any side effects, authentication requirements, or response format. It also doesn't clarify how the 'action' parameter changes behavior beyond the schema enum.

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, front-loaded sentence precisely captures the tool's purpose with no filler. It is minimal but effective.

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 simple tool with two well-documented parameters, the description is minimally adequate. However, it does not explicitly state the output type (a URL string vs. a JSON object) or address error scenarios. The lack of an output schema makes this more critical, so a 3 is given.

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 input schema documents both parameters with descriptions and enum values, achieving 100% coverage. The description adds no additional meaning or context to the parameters, so baseline 3 is appropriate.

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 clearly states the tool retrieves a link to a call recording, specifying the verb 'get' and resource 'recording'. It is distinguishable from siblings like get_calls (list of calls) and get_users (list of users) by its focus on a specific recording. However, it doesn't explicitly mention it operates by recording ID, though that is implied by the required parameter.

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 provides no guidance on when to use this tool versus alternatives, nor when to choose the 'play' vs 'download' action. Sibling tools like get_calls exist, but the description doesn't mention any conditions that would select this tool over them.

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