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

Annotations already declare this is a safe read (readOnlyHint=true, destructiveHint=false), so the bar is lower, yet the description still adds value: it discloses the auth requirement (Cotlet API key with app access) and, since there is no output schema, enumerates the returned settings including Guest Questionnaire questions.

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 field list is effectively stated twice ("Full event: title, description..." then again "guest limit, waitlist, Guest Approval"), which is redundant. The usage and auth sentences earn their place, but the opening is bloated.

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?

With no output schema, the description compensates by enumerating the returned fields, and it adds the auth prerequisite and a cross-tool usage hint. Adequate for a single-parameter read tool, though it omits any note on pagination or errors.

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 coverage is 100% and the single event_id parameter is documented as coming from list_events, so the schema carries the burden. The description adds nothing about the parameter format, so baseline 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?

States a specific verb (get) and resource (Partiful event) and enumerates the fields returned, so an agent knows this is a single-event detail fetch. It does not explicitly contrast itself with partiful_list_events, but the enumerated settings fields make the scope evident.

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?

"Use it before update_event to see what is set now" gives a concrete sequencing rule and names the sibling tool it complements. No when-not guidance is offered (e.g., compared with list_events), but the usage context is clear.

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