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

With readOnlyHint=true already declaring the safety profile, the description adds real context: what the records represent (dial-plan audio assets), what each entry carries (name, description, duration, usage location), and the backing endpoint. It says nothing about pagination defaults or result volume, but the schema covers those.

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?

Two sentences, both earning their place: the first defines scope and return contents, the second prevents the most likely misidentification. Front-loaded with the core verb and resource.

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?

No output schema exists, and the description compensates by enumerating the fields each recording exposes and its usage context. Paging and sorting semantics live in the schema, so the only residual gap is behavior at scale (total counts, result caps).

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% with all four optional paging/sort parameters fully described (defaults, ranges, enums), so the schema does the heavy lifting. The description adds no parameter-level meaning beyond that, which is the baseline case.

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 and resource ('List the uploaded audio recordings used in the dial plan'), enumerates the subtypes (greetings, announcements, voice-over scripts), lists the fields returned, and gives the underlying endpoint. The explicit 'Not call recordings' line separates it from the call-recording siblings in the same namespace.

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 'Not call recordings' exclusion and the 'used in the dial plan' scoping give a clear condition for when this tool is right rather than rinkel_get_call_recording_url. It stops short of naming the alternative tool explicitly, so the agent must infer the routing rather than being handed it.

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