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

Going beyond the annotations (readOnlyHint=false, openWorldHint=true, destructiveHint=false), it discloses that the action sends an email to a real third party, that the recipient only sees the itinerary after accepting, and that it needs a Cotlet API key with app access. It adds the confirm-each-call default and the ability to switch it off, which the annotations do not convey.

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?

Purpose is front-loaded, which is good, but the confirmation guidance is stated twice ('By default you confirm each call; you can switch that off' and 'confirm with the user before each call'), and the email-passing clause repeats the opening sentence. Some tightening would improve it.

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 simple two-parameter invite tool with annotations covering the safety profile and no output schema, the description covers the external side effect, the recipient flow, the confirmation requirement, and auth needs. Only the when-to-use versus siblings is missing.

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 parameters (email, trip_id) are already documented in the schema. The description paraphrases the email parameter ('the email you pass') but adds no format or constraint detail, so 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?

States a specific verb and resource ('Invite someone by email to collaborate on the trip') and clarifies the mechanism ('sends the invitation for the trip to the email you pass'). An agent can distinguish it from other wanderlog siblings such as add_place or create_trip 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?

The description gives behavioral guidance about confirmation ('by default you confirm each call... confirm with the user before each call') but never states when to use this tool versus alternatives, nor any precondition beyond having the trip_id. Usage is implied rather than explicitly scoped.

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