listEvents

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

With no annotations provided, the description carries the transparency burden. 'List' clearly indicates a read-only operation, but the description does not disclose behavior such as pagination defaults, result ordering, or whether all events or only user-scoped events are returned. This is minimal but acceptable for a simple list operation.

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 two short sentences, front-loaded with the primary action and followed by a list of example filters. Every word earns its place, and there is no redundant padding or unnecessary detail.

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 7 optional parameters and no output schema, the description is adequate but incomplete. It does not explain pagination parameters (next, offset, limit) or how filters interact, and it does not guide agents toward related tools like listEmEvents. The schema helps, but the description alone leaves meaningful gaps.

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 input schema covers 100% of parameters with descriptions, so the baseline is 3. The description mentions a few filter examples (personId, type, propertyAddress) but adds no meaning beyond what the schema already provides. The 'etc.' is vague but does not compensate for the lack of additional parameter 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 clearly states the tool lists events and mentions key filterable fields (personId, type, propertyAddress), making the core action and resource explicit. However, it does not differentiate this from the sibling listEmEvents tool, so it falls short of a 5.

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 this tool is for listing events with optional filters, but it offers no explicit when-to-use or when-not-to-use guidance, nor does it point to alternatives like getEvent for single events or listEmEvents for email events. The usage context is only implied.

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