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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, and the description's 'Read-only' simply repeats that. It adds the REST endpoint path, which is mild context, but says nothing about result volume, refunds/excluded statuses, or rate limits beyond the safety profile the annotations already supply.

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 substantive content is one front-loaded sentence with zero padding. The trailing 'Read-only. GET /events/{eventid}/transactions.' fragments are short but partly redundant with the annotations already shown to the agent.

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?

With no output schema, the description usefully names the returned fields (order reference, checkout id, date, amount, ticket count, status), and pagination is fully covered by the schema. It omits sorting behavior and any note on which order statuses are included, so it is close to but not fully complete.

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%: limit, offset (including the 'pass next_offset' pattern) and event_id are all documented in the schema itself. The description adds no parameter-level meaning, so the baseline of 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?

States a specific verb (List) plus resource (orders/transactions) scoped to 'one event', and enumerates the returned fields, so it is clearly distinct from eventzilla_get_transaction and eventzilla_list_event_attendees in substance. It never names a sibling explicitly, so it falls just short of the top mark.

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 one-event scope: use this to enumerate an event's orders. There is no explicit when-to-use/when-not guidance and no pointer to the singular eventzilla_get_transaction for a single order, so an agent must infer the boundary itself.

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