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

Annotations already declare readOnlyHint=true, so safety is covered. The description usefully discloses that the payload contains sensitive items — coach credentials and personalized ticket links — which hints at handling care, but it says nothing about whether the party data is cached, per-user, or how credentials are scoped. The title also advertises a 'Drop Wave Schedule' that the description omits, a minor inconsistency with the structured title.

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 compact sentence, front-loaded with the verb and the most important return item. Slightly compressed to the point of being a bare field list, with no framing sentence about what the profile represents.

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 carries the burden of explaining return shape, and it does so only as a short field list. It omits the drop/wave schedule promised by the title and gives no indication of the response structure (a single profile object vs. per-member entries) — enough to select the tool, not enough to predict its output.

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, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies a no-argument call returning the full profile.

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 opens with a specific verb ('Get') and enumerates the exact resources returned: traveling party roster, ticket links, preferred headliner rides, and MDE credentials. It is clearly distinguishable from siblings like get_live_waits or get_dining_availability. However, it never explains what the 'Benson party' is (a named group? the user's own party?), which leaves the scope slightly ambiguous.

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?

No guidance on when to call this versus alternatives, no prerequisites, and no exclusions. The description is a pure content list; an agent must infer that it should call this when it needs party/identity context rather than live operational data.

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