Get Event Guests

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

The annotations already declare the tool read-only, idempotent, and non-destructive. The description adds a small behavioral note about external platform access permissions, which goes beyond the annotations. However, it does not explain failure behavior, authentication requirements, or data-sensitivity implications.

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 description is a single sentence with no wasted words. It front-loads the core action and resource. The qualifier about platform permission is somewhat vague but does not make the description bloated.

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?

There is no output schema and the description does not mention return shape, pagination, or what fields a guest entry contains. The 'when the platform permits access' caveat lacks specifics about error handling or denial outcomes. An agent has enough to attempt a call but not enough to anticipate the response or edge cases.

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?

The input schema already documents event_id, platform, and ticket_key with descriptions, and limit has constraints. The description itself adds no parameter-level meaning. With 75% schema description coverage, the schema carries most of the parameter burden, so a baseline score of 3 is appropriate.

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?

The description states a clear action and resource: 'Get an event guest list.' The title confirms the purpose. It does not explicitly compare itself to sibling tools like get_event or list_events, but 'guest list' is a distinct enough resource that an agent can infer the scope.

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 guidance is given for when to use this tool versus get_event, list_events, or search_events. The phrase 'when the platform permits access' is a permission caveat, not an actionable usage guideline. There are no stated prerequisites, alternatives, or exclusions.

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