calls_list

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

No annotations are provided, so the description carries full burden. It doesn't disclose whether this is a read-only operation, whether it requires authentication, what the return format looks like, whether it supports pagination, or any rate limits. The mention of 'optional filtering' hints at some behavior but lacks specifics.

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 a single, efficient sentence that gets straight to the point. However, it's arguably too concise given the complexity of 5 undocumented parameters and lack of sibling differentiation.

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 tool with 5 parameters (0% schema coverage), no annotations, no output schema, and many sibling alternatives, the description is incomplete. It doesn't explain the tool's behavior, parameter usage, or differentiation from similar tools, leaving significant gaps for an AI agent.

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?

With 0% schema description coverage for 5 parameters, the description doesn't compensate at all. It mentions 'optional filtering' but doesn't explain what parameters control filtering (limit, after, properties, associations, archived) or their meanings. The schema provides structure but no semantic context.

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 'List all calls with optional filtering' clearly states the verb ('List') and resource ('calls'), but it's vague about scope and doesn't distinguish from sibling tools like calls_search or calls_get. It mentions 'optional filtering' but doesn't specify what kind of filtering is available.

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 about when to use this tool versus alternatives like calls_search, calls_get, or other list tools (emails_list, meetings_list, etc.). The description mentions 'optional filtering' but doesn't clarify when this tool is appropriate versus more specialized search tools.

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