evite_list_guests

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

The readOnlyHint annotation already indicates a safe read operation, lowering the bar. The description adds the endpoint and the fields returned, which is useful context but doesn't disclose additional behavioral traits like pagination, ordering, or error conditions. It does not contradict annotations.

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?

A single, front-loaded sentence that states the action, resource, endpoint, and representative output fields. Every word contributes value, and there is no redundancy or fluff.

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 simple read-only list tool with one parameter and no output schema, the description adequately covers the tool's core function and return content. It lacks mention of pagination or result limits, but these are not critical for a basic list operation, and the readOnlyHint plus clear purpose make it sufficiently 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?

The input schema has 100% coverage, with the parameter event_id fully described and even noting its provenance from evite_list_events. The description itself adds no parameter information beyond what the schema already provides, so the baseline 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 clearly states the tool lists guests for an Evite event, with a specific verb ('List') and resource ('guests for an Evite event'). It also enumerates returned details (name, RSVP response, head counts, delivery status), distinguishing it from sibling tools like evite_list_events (lists events) and evite_rsvp_summary (likely summarizes RSVPs).

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?

The description implies when to use: when you need guest details for a specific event. It also notes the event_id comes from evite_list_events, providing a clear prerequisite. However, it does not explicitly contrast with alternatives such as evite_rsvp_summary or evite_get_event, so it falls short of full exclusion guidance.

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