teamleader_events_list

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

With no annotations provided, the description carries the full burden. It confirms the read-only action and filter options, but does not disclose pagination behavior, whether filters combine with AND/OR, the scope of events returned (e.g., all users vs. only authenticated user), or the response structure. For a list operation with six optional filters, these are significant gaps.

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 with no filler, making it easy to parse and directly conveying the core action and filter support.

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?

Given the absence of an output schema and annotations, the description is too thin to fully support invocation. It does not indicate what fields are returned in the list, whether there are pagination limits, or how the optional filters interact (e.g., AND/OR semantics). The parameter schema is thorough, but the tool's behavior and output remain under-specified.

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 descriptions cover 100% of the parameters with format details. The description's mention of 'date range, contact, company, or deal' merely summarizes the parameter names already present in the schema, adding no additional semantic value beyond what the schema 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?

The description uses the specific verb 'List' and clearly identifies the resource as 'calendar events from Teamleader Focus', with a concise enumeration of filter dimensions. This clearly distinguishes it from sibling tools like teamleader_event_info (single event) and teamleader_event_create.

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 gives clear context that this tool is for listing events with optional filters, implying broad retrieval use. However, it does not explicitly state when to prefer teamleader_event_info for a single event or mention any exclusions, so it stops short of explicit alternative guidance.

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