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

Beyond annotations (readOnlyHint true), description adds 'Read-only' and reveals that host role is required. Also mentions totals and checked-in count, hinting at return structure. No contradictions with 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?

Two sentences covering all essential information: what is listed, optional filter, requirements, and read-only nature. No wasted words, front-loaded with key details.

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?

Lacking output schema but description mentions fields and summary counts. Specifies host requirement. For a read-only list tool with strong annotations, this is adequately complete, though pagination or response format could be added.

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?

With 0% schema description coverage, the description adds meaning to 'category' as optional filter, but does not elaborate on event_id beyond being required. Partially compensates but event_id remains minimally described.

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?

Clearly states listing guests with specific fields (name, email, phone, category, plus-ones, check-in status) and summary totals. Distinguishes from sibling tools like add_guest, edit_guest, remove_guest.

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?

Explicitly requires event_id and host role, and declares read-only. While it doesn't name alternative tools for mutations, the condition 'requires event_id; you must be a host' sets clear usage boundaries.

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