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

Annotations declare write, non-destructive, non-idempotent. The description adds latency (10-20 seconds), a privacy guarantee (only airports, headcounts, dates, and budget are sent), and what happens next (group opens link and votes). No contradiction with annotations.

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 front-loaded with the primary use case, then layers in prerequisites, ranking details, privacy, and latency. It is longer than average but each sentence contributes necessary context; minor tightening could 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 7-parameter tool with nested origins and no output schema, the description covers when to use, what to send, what is returned (a link), latency, and privacy. It is complete enough for an agent to call correctly.

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 71%, and the description explains origins (city/airport and headcount), start_date (use a Friday in the season), and destinations (2-6, omit for top 10). Nights and passport are left to the schema, but the description meaningfully clarifies key parameters.

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 a specific action (creates a voting link) and resource (group trip) and distinguishes itself from find_warm_destinations by positioning itself as the voting step rather than destination search.

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?

It gives clear when-to-use examples, prerequisites (ask for origins before suggesting places), and alternatives (find_warm_destinations or own shortlist). It does not mention sibling plan_group_trip, so it stops short of full sibling differentiation.

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