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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds that the response includes guests and their RSVPs, which is useful scope information beyond annotations, but it also redundantly repeats 'Read-only' and provides no permission, pagination, or freshness details.

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 only two short sentences and front-loads the key scope ('one event and its guests with their RSVPs'). However, the second sentence ('Read-only') duplicates an annotation and does not earn its place as strongly as the first sentence does.

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 an output schema present and rich annotations, the description does not need to explain return values. It gives enough context to know this retrieves a single event with guest/RSVP data. The missing piece is usage guidance against list/search siblings, which is a separate dimension.

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 both required UUID parameters are already documented in the schema. The description adds no parameter-specific meaning, which is acceptable given full schema coverage but does not exceed the baseline.

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 the resource ('one event') and what it includes ('its guests with their RSVPs'), which is specific enough to distinguish it from list-style siblings like fundraising_list_network_events. It lacks an explicit verb, but the name and title supply that. The only gap is that it does not name a sibling alternative explicitly.

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?

There is no guidance on when to use this tool versus alternatives such as fundraising_list_network_events, nor any prerequisites or exclusions. 'Read-only' is a safety property, not usage guidance. The agent is left to infer the use case from the name alone.

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