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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely new context: the tool performs no browser action itself, returns a screen/button/field walkthrough, and requires a follow-up browser session. The note that Partiful has no public API explains why an agent must drive the UI.

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 core workflow is front-loaded and efficient, but the final sentence is a sentence fragment ('Partiful's official API: ...') with an oddly future-dated verification stamp (11 Oct 2026) that consumes space for little operational value. The opening clause restates the title rather than adding information.

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 zero-parameter, no-output-schema tool, the definition covers what matters: no side effects, a returned procedure, the required follow-up browser tools, and the absence of an API. The one residual gap is that it never states how the returned guide is shaped or whether state is checked afterward.

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 tool takes zero parameters and the schema is fully described, so there is no parameter meaning to add. The description correctly spends no space on inputs and instead clarifies the output contract.

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 does state a concrete resource (RSVPs in the user's own Partiful account) and discloses that the tool returns a step-by-step procedure rather than opening anything itself. However, the opening claim 'List RSVPs' sits in tension with the actual behavior ('returns how to do it ... opens nothing by itself'), so an agent may still be unsure whether real RSVP data comes back. No differentiation from sibling partiful_export_guest_list is offered.

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?

It tells the agent exactly what to do after calling: perform the steps with the cotlet_browser_* tools in the user's Partiful Cloud Browser. Scope is restricted to the user's own account, which is useful. It stops short of naming when an agent should prefer partiful_export_guest_list or partiful_create_invite instead.

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