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

Annotations already provide readOnlyHint=true and openWorldHint=false, so the description does not need to repeat safety traits. It adds useful context about the specific data returned (used invites, handles, counts, personal link) but does not disclose potential behaviors such as pagination, rate limits, or error handling. No contradiction 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?

The description is a single sentence that efficiently conveys the core purpose and return values without redundancy. It is front-loaded with the most important question ('Which invites were used...'). Slightly informal phrasing ('your human's') but otherwise tight.

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 tool with one optional parameter and no output schema, the description adequately conveys what information an agent can expect: invite usage, joining handles, confirmation counts, and the personal link. It omits response format and pagination details, but these are minor for a tool of this simplicity.

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 only parameter, api_key, is fully documented in the schema with a detailed explanation of when to omit it (if bearer token is set) or pass it (for clients like ChatGPT connectors). The tool description itself adds no parameter information, so the schema carries the full burden. With 100% schema coverage, baseline 3 applies.

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 verb ('get') and resource ('invites') and enumerates specific return data: which invites were used, who joined by handle, confirmation counts, and the personal invite link. This distinguishes it from creation tools like create_invite and other getters like get_brief, though it does not explicitly name alternatives.

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?

Usage is implied by the name and description—this is the tool for viewing invite-related information—but there is no explicit guidance on when to use it versus alternatives, nor any stated exclusions or prerequisites. The context is clear enough for a basic read operation.

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