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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds that results are scoped to the account and cites the underlying endpoint 'GET /events', but says nothing about permissions, rate limits, or pagination behavior even though the schema hints at a next_first_result. Adequate, not rich.

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 with zero redundancy: what it returns, what it filters on, and how the id is reused. Purpose is front-loaded before filters and the hand-off, which is the right order for scanning.

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 10-parameter read tool with full schema coverage, full annotations and no output schema, the definition covers purpose, returned fields, filtering and the event-id hand-off. The only shortfall is that pagination (next_first_result, total counts) is left entirely to the schema rather than being explained in prose.

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 ten parameters are already documented with formats, enums, defaults and the next_first_result pagination hint. The description only restates the filter categories (title partial match, status, start/end/creation dates) without adding semantics beyond the schema, so the baseline 3 applies.

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?

Specific verb+resource ('List the events of the Evenium account') with the returned fields spelled out (id, title, dates, status, creation date) and the supported filters named. It is clearly a collection query, but it never explicitly distinguishes itself from the sibling evenium_get_event, so the agent must infer single-vs-many from the names.

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?

Usage is implied by the filter list and by the forward hand-off 'Use an event id with the guest and session tools', which tells the agent this is an entry point. There is no explicit when-to-use/when-not statement and no named alternative for the single-event case.

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