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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds the status vocabulary (CONFIRMED, DECLINED, CANCELED), which is genuinely useful, but says nothing about behavior for a guest with no registration or an invalid contact id.

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?

Two tight sentences with the purpose front-loaded and examples immediately after. The trailing endpoint reference is mildly redundant given the schema, but costs little.

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 two-parameter read-only lookup this is close to adequate, and the example status values partially compensate for the missing output schema. It still leaves unclear whether the response is the status alone or a broader guest object, and how it differs from the post-status tool.

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% and both parameters document the `ext:` alternate-id forms, so the schema carries the load. The description's `{eventId}/{contactId}` path notation merely mirrors those parameters without adding format or constraint detail.

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+resource ('registration status of one guest at an event') and even enumerates example values, so the retrieval is unambiguous. It does not, however, distinguish itself from close siblings like evenium_get_guest or the easily-confused evenium_get_guest_post_status.

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?

No indication of when to use this versus evenium_get_guest (full guest record) or evenium_get_guest_post_status (a different status dimension). Given how similar the sibling names are, the absence of routing guidance is a real gap.

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