teamleader_list_events

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It only states that it lists events with filtering and pagination, but doesn't disclose nuances like whether this is a read-only operation (which is implied by 'list'), what the return format is, how pagination works beyond defaults, or any rate limits or authentication requirements. It describes the obvious behavior but not the deeper behavioral context.

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, clear, and concise sentence that front-loads the core purpose (list events) and mentions optional filtering and pagination. It's appropriately sized and avoids unnecessary detail, though it could be slightly more explicit about the filtering parameters.

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 tool's moderate complexity (6 parameters, all optional) and the lack of an output schema, the description is adequate but incomplete. It covers the basics (list, filter, paginate) but doesn't explain how to combine filters or what the response looks like. Without annotations, an agent might not know that the operation is safe or how many events are returned per page beyond max.

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 schema already describes all 6 parameters with 100% coverage, so the baseline is 3. The description adds no additional parameter semantics beyond saying filtering exists, which is redundant with schema. It doesn't clarify how the date parameters interplay (e.g., if both start and end filters are needed) or provide examples of usage.

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 resource 'calendar events' from Teamleader Focus, and mentions filtering and pagination, which differentiates it from siblings like teamleader_get_event (singular get) and teamleader_create_event. However, it doesn't explicitly mention available filters, which are only in the schema.

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 does not provide any guidance on when to use this tool versus alternatives. It doesn't mention that this is a list operation as opposed to get_event for a single event, nor does it discuss any exclusions or prerequisites. No context is given about typical use cases or how it relates to sibling tools.

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