list_voice_executions

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

With no annotations, the description carries the burden of behavioral disclosure. It mentions the tool lists live and historical executions and optionally filters by status, but does not disclose authentication needs, effect on state, or output behavior beyond listing. Since it is a read operation, the lack of disclosure is a minor gap.

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 extremely concise: one sentence for purpose, followed by a brief parameter list. No unnecessary words, front-loaded with the main action. Every sentence 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?

Given the tool's simplicity (2 optional parameters, output schema exists), the description is minimally adequate. It covers parameters but lacks usage guidance and behavioral context. For a simple list tool, it suffices but could add value with pagination details or error conditions.

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%, but the description adds meaning: 'status' filter values (active, completed, failed, transferred) and 'limit' as 'Max results'. This goes beyond the schema's type-only definitions. However, it does not explain default behavior or the meaning of each status.

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 verb 'List' and the resource 'voice agent executions', and clarifies it includes both live and historical phone calls. However, it does not explicitly differentiate from sibling tools like get_voice_execution or list_voice_pending_approvals.

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?

No guidance is provided on when to use this tool versus alternatives like get_voice_execution for a specific execution or list_voice_pending_approvals for pending ones. The description only lists parameters without contextual usage advice.

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