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

Annotations already declare this is a read-only, non-destructive, open-world operation. The description adds important behavioral context beyond annotations by disclosing that filtering happens after the full list is read, which has performance implications, and that pagination should be used for large events.

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 tight sentences: the resource and returned fields are front-loaded, followed by the filtering/pagination caveat and endpoint. No sentence is wasted.

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?

No output schema exists, and the description usefully lists the main returned fields. It does not describe the response envelope or pagination metadata explicitly, but the offset parameter references next_offset, which covers the key pagination detail.

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 coverage is 100%, so the schema already documents each parameter. The description still adds useful meaning by explaining that filters are applied after the full list is read and that limit/offset are the mechanism for large events.

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?

Identifies a specific resource, event registrations, and enumerates what is returned: status, group, contact details, and form answers. It also distinguishes registrations from generic participants by saying “people who registered or were pre-registered,” though it does not explicitly name the sibling list tool to use instead.

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 one clear operational guideline: filters are applied after the full list is read, and limit/offset should be used for large events. It does not explain when to use this tool instead of sibling tools such as list_participants or list_groups.

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