list_calls

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

Annotations already declare read-only and open-world hints. The description adds value by specifying the return payload is minimal metadata (ID, title, date, duration) and that date filtering is supported, giving context beyond the annotations.

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 that are front-loaded with the core purpose, followed by return info and alternative guidance. Every sentence contributes meaningful content without redundancy.

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?

The description sufficiently covers the tool's purpose, return behavior, and alternatives for a listing function. Pagination and workspace filtering are documented in the schema, and the annotations cover safety and world assumptions, making it complete for tool selection.

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?

The input schema covers all four parameters with detailed descriptions, so the baseline is 3. The description only mentions 'optional date filtering', which adds no new semantic detail beyond what the schema already provides for fromDateTime/toDateTime.

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?

Clearly states it 'List Gong calls' with a specific verb and resource. The mention of 'optional date filtering' scopes the functionality, and the directive to use get_call_summary or get_call_transcript for other needs distinguishes it from sibling 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?

Provides explicit alternatives for when details or transcripts are needed, guiding tool selection. However, it does not explicitly mention when to use list_calls versus search_calls or other search variants, so it falls short of a full exclusion set.

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