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

Annotations already cover the safety profile (readOnlyHint, destructiveHint false, openWorldHint), so the bar is lower. The description adds genuinely new behavior: it discloses the auth requirement ('Cotlet API key with access to this app'), that the output is a file link rather than inline rows, and that Guest Questionnaire answers are included in the file.

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 is front-loaded, but the second and third sentences restate the same idea ('the same file as the Export CSV button' / 'a link to the CSV that Partiful's Export CSV button produces'), which is redundant. The trailing auth sentence is useful but tacked on.

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 read-only export tool with annotations covering safety and no output schema, the description supplies what is needed: the return form (a CSV link), the content scope (filtered RSVPs plus questionnaire answers), and the credential requirement. Nothing critical is missing, though it could note that the link is what the caller must fetch next.

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?

Schema description coverage is 100%, so the schema already documents both parameters (event_id and the statuses enum list). The description adds only a light restatement ('limited to the RSVP statuses you choose'), which reinforces the filter intent but contributes no syntax or default detail beyond the schema.

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?

States a specific verb+resource: it returns the guest list as a CSV file link, explicitly equated with Partiful's Export CSV button output. An agent immediately knows this is an export operation, not a raw listing, and the scoping to chosen RSVP statuses is stated up front.

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 describes a downstream scenario ('your agent or n8n flow reads the file and appends the rows to a sheet or CRM'), which implies when the tool is useful. However, it never contrasts with the sibling listing tool (partiful_list_guests) or states when NOT to use it, so guidance is contextual rather than explicit.

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