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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. What the description adds beyond them is return-content disclosure — the list of data groups the agent will get back — which is valuable because no output schema exists. It does not say what happens for an unknown or deleted id (empty result vs error), which is the remaining behavioral gap.

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?

One front-loaded sentence opening with 'Everything about one invitation', then a dense enumeration of fields. The enumeration is long but each item earns its place as return-value disclosure in the absence of an output schema. No filler, no restating of the title.

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 one-parameter read tool with no output schema, enumerating the returned data is exactly the right compensation, and annotations cover the safety profile. Completeness is only slightly short: missing-state behavior (bad/deleted id) and any indication of whether the payload is nested or large are unstated.

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% with a single required integer id whose description already says it comes from search-guests. The description adds no syntax, format or constraint information about the id beyond what the schema provides, so the 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 names a specific retrieval target ('one invitation') and enumerates exactly what is returned: household size and children, contact details, postal address, per-moment answers, dietary notes, message, RSVP question answers and personal RSVP link. That is far more specific than the title. It stops short of naming a sibling such as search-guests (which only appears in the schema parameter text) or distinguishing itself from update-guest/delete-guest, so it is clear but not fully differentiated.

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 when-to-use or when-not-to-use guidance anywhere in the description. Read-only single-record lookup is implied by 'one invitation', and the schema mentions 'from search-guests', but the description itself never routes the agent between fetching, searching, updating or deleting a guest.

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