List VoiceAI Runs

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

The readOnlyHint annotation already declares this a safe non-mutating read, so the description adds the useful ordering detail ("newest first"). However, it says nothing about default results count, pagination, or return shape, and gives no explanation for why a read-only listing tool accepts an out_dir parameter.

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 efficient sentence with the key qualifier ("newest first") front-loaded and no filler. It is appropriately sized, though it errs toward under-specification rather than over-verbosity.

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 listing tool with no output schema, the description should at least bound the result set and explain out_dir. With two undocumented parameters, no pagination detail, and an unexplained write-like parameter on a readOnly tool, an agent lacks what it needs to invoke this confidently.

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 0% and the description mentions neither parameter. limit is loosely implied by "recent" but the cap (max 100) and default are not addressed, and out_dir — an unexplained output-directory argument on a read-only list tool — is entirely undocumented in both schema and description.

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 gives a specific verb ("Lists") and resource ("VoiceAI analysis runs") plus ordering ("newest first"), so an agent knows exactly what it returns. It does not explicitly differentiate itself from siblings like ctm_voiceai_run_status or ctm_voiceai_get_calls, which is the only reason it falls short of a 5.

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 guidance on when to use this versus ctm_voiceai_run_status (single run) or ctm_voiceai_get_calls. "Recent" is undefined — no bound on how many runs are returned or how far back "recent" reaches, leaving the agent to infer selection criteria.

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