evite_list_events

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

The readOnlyHint annotation already establishes the safety profile; the description adds that this is a GET endpoint and returns events plus a totals breakdown. It doesn't disclose deeper behavior like pagination details or response structure beyond the totals note, so it adds moderate but not rich 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?

Three short sentences cover the action, the return shape, and the guest-filter mode with no filler or repetition of schema content. Every sentence earns its place and the main action is front-loaded.

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 simple read-only listing tool with no required parameters and a fully documented schema, this is nearly complete. Since there is no output schema, the description helpfully notes that the response contains events plus a totals breakdown. It could have explicitly routed the agent to alternatives, but the low complexity makes that a minor gap.

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%, so all six parameters, their defaults, enums, and constraints are already documented. The description's filterBy=others note adds no real meaning 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 states a specific action and resource: 'List your Evite events' with the REST endpoint GET /services/events/v1/. This clearly distinguishes it from related tools like evite_get_event and evite_list_guests.

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?

It clearly establishes this as the tool for listing the caller's Evite events and explicitly calls out the filterBy=others guest-mode use case. It doesn't name alternative tools for other operations, but the list semantics and sibling tool names make the boundary clear.

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