teamleader_calls_list

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

With no annotations, the description carries the burden of disclosing behavior. It mentions that filtering is optional, which implies unfiltered calls when no filter is provided. However, it does not disclose pagination behavior, default page size, or return structure. The read-only nature is implied by 'List' but not explicit.

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 succinct sentence that conveys the core purpose and key option. There is no redundant wording or unnecessary detail, making it appropriately concise.

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 no output schema and no annotations, the description lacks essential context. It does not explain the return format, pagination options, or the dependency between filtering parameters. The agent would need to infer too much about how to correctly invoke the tool with filters.

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 coverage is 75%, with three of four parameters described. The description adds only the concept of customer filtering, which is already present in the schema via customer_id and customer_type descriptions. It does not clarify the missing 'page' parameter or the requirement to use customer_id and customer_type together.

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 'calls', and mentions an optional filter by customer. This distinguishes it from sibling tools like teamleader_calls_create and teamleader_calls_complete, making the purpose unambiguous.

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?

The description implies that the tool lists calls and can be filtered by customer, but does not explicitly state when to use it vs alternatives. It also fails to mention the mutual dependency between customer_id and customer_type, which is crucial for correct invocation. No alternative tools are referenced.

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