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

readOnlyHint=true already tells the agent this is a safe read, so the description's added domain context is the differentiator: it explains what a recording represents and flags that only processed recordings are callable, which is a real behavioral constraint an agent would otherwise have to discover. It does not describe pagination or empty-result behavior, but the schema covers paging.

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 short clauses: the core action with a clarifying gloss and field list, then the one constraint that matters. No filler, and the resource identity is front-loaded.

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?

With no output schema, the field enumeration (id, name, type, length, processed) does useful work in telling the agent what a result looks like, and the processed flag requirement is stated. What remains missing is any hint about result volume or paging from the description itself, which is minor for a simple read-only list 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 description coverage is 100% and both parameters (limit, start) are fully documented in the schema, including the next_start paging convention. The description adds nothing about them, so the baseline 3 applies.

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 voice recordings") and parenthetically defines what a recording is in this domain, plus enumerates the fields returned. It does not explicitly distinguish itself from the sibling dialmycalls_get_recording or dialmycalls_create_recording_tts, but the plural 'List' versus 'get' convention and the field listing make the intent unambiguous.

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?

There is no explicit 'use this when...' statement and no named alternative such as get_recording for single-record retrieval. The sentence "A call needs a processed recording" does imply the practical use case (finding a usable recording id to pass to send_call), which goes beyond a bare description but leaves the routing to inference.

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