teamleader_list_events

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

With no annotations, the description carries the full burden. It discloses that the tool supports filtering and pagination, which is useful, but it does not explicitly state that this is a read-only operation, nor does it describe any authentication requirements, rate limits, or response behavior beyond listing.

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, front-loaded sentence: 'List calendar events from Teamleader Focus with optional filtering and pagination'. It is concise, contains no redundancy, and every word adds value.

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 tool has no output schema, so the description would need to explain what the response contains, but it does not. The parameter details are covered by the schema, yet the description leaves the return format and pagination behavior unstated, making it adequate but incomplete.

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 100% for all six parameters, so the baseline is 3. The description only summarizes this as 'optional filtering and pagination', adding no new meaning beyond what the schema already provides for each parameter.

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 it lists calendar events from Teamleader Focus, which is a specific verb+resource combination. It distinguishes from sibling tools like teamleader_get_event (single event) and teamleader_create_event (create), and from other list tools like meetings_list and calls_list.

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 mentions optional filtering and pagination, implying it is for reading multiple events, but provides no explicit guidance on when to use this tool versus alternatives such as teamleader_get_event for a single event. No exclusions or alternatives are named.

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