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

Annotations already declare openWorldHint and destructiveHint, but the description explains the actual mechanism: guest invitations send email that cannot be unsent and grant external recipients trip access, and this applies even when invitations are optional. That is genuine added context beyond the boolean hints, though the "Open-world:"/"Destructive:" framing restates the annotation labels.

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?

Front-loaded correctly (creation, then invitations, then trip type, then cover image, then safety), but the Unsplash URL warning is restated twice in prose plus again in the schema, and the safety section repeats annotation labels. Roughly a third of the text is redundant.

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?

Covers the nontrivial risk surface (external email, irreversible invitations) and the two cover-image pitfalls for a 10-parameter create tool with an output schema and full annotations. Nothing critical is missing, though it doesn't say what the required minimum for a valid trip is (everything is optional).

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%, so baseline is 3, but the description adds meaning the schema cannot: it reveals that data.guest_invites is the key that triggers email invitations, which is invisible in the untyped `data` object. The planned-vs-leisure field groupings and URL shape rules largely duplicate the schema's own parameter descriptions.

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?

Opens with a specific verb+resource ("Create a Tripsy trip") and immediately differentiates the invitation path from the sibling tripsy_collaborators_invite, which handles existing trips. An agent can identify the tool's scope without opening the schema.

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?

Gives explicit routing (guest_invites at creation vs. tripsy_collaborators_invite for existing trips) and branch guidance for planned itineraries vs. leisure trips. It doesn't mention checking trips_list for an existing trip before creating a duplicate, but the alternative-tool guidance is clear.

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