List Voice Call Events

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

Annotations already mark readOnlyHint=true, and the description adds cursor-paginated behavior and the strict parameter allowance ('only cursor, limit, and call_id'), which are not in annotations. It does not describe rate limits or ordering but adds meaningful constraints beyond the structured data.

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?

Three concise, front-loaded clauses: endpoint and action first, then definition and constraint. No filler and every sentence contributes useful information.

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 read-only cursor-paginated list with complete schema, the description adequately defines the resource, pagination, and parameter restriction. It does not detail the return shape, but no output schema exists and sibling get_voice_call_event likely covers event details.

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?

Input schema covers all three parameters with descriptions, so baseline is 3. The description adds only the 'only' restriction and cursor-paginated framing; it does not elaborate on parameter semantics beyond what the schema already provides.

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 'List voice call events' with the endpoint path, defines events as 'discrete occurrences during the lifecycle of voice calls,' and cursor-paginated scope differentiates it from single-event retrieval and call listing tools.

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?

Implies usage for listing events and filtering by call_id, but does not explicitly state when to prefer this over alternatives or mention tools like get_voice_call_event or list_voice_calls. The 'accepts only cursor, limit, and call_id' constraint provides some selection guidance but no exclusions.

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