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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: newest-first ordering, the fact that archived events are excluded by default, and that each record carries nested configuration (ticketGroups, ticketTypes, fields). It stops short of saying anything about result caps or cursor mechanics for the list as a whole.

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 tightly packed sentences, front-loaded with the verb, resource and ordering before the routing guidance. No filler and no repetition of schema-level parameter documentation.

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?

An output schema exists, so return-value explanation is unnecessary, and the description still summarizes what each record contains. Combined with complete schema coverage and explicit sibling routing, an agent has everything needed to select and call this tool correctly.

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%, with limit, search, status, testmode and both cursors fully documented in the schema itself. The description's only added parameter-relevant content is the archived-by-default behavior, which the status schema description already states verbatim. Baseline 3 is appropriate when the schema does the heavy lifting.

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 and resource ('List the event pages on the Checkout Page account') plus scope details (newest first, full configuration including ticket groups/types/fields). It explicitly disambiguates from the similarly-named siblings by noting that checkout pages and forms are separate page types.

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?

Gives the downstream use case clearly: 'this is how to find an event id for get_event, update_event, list_bookings and list_tickets'. It also names the two alternative tools for other page types and explains the archived-status default, so when-to-use and when-not-to-use are both covered.

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