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

No annotations are provided, so the description carries the full behavioral burden and falls short. It never states whether this is a read/search or a mutation, what the 'strict coastal verification' actually enforces, or any pricing, availability, or auth implications. Only the vague verification phrase adds anything beyond the name.

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?

It is a single front-loaded sentence with no wasted words, but the brevity stems from under-specification rather than disciplined concision for a 7-parameter tool.

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 43% schema coverage, no annotations, no output schema, and no stated action verb, the description leaves major gaps an agent needs before invoking it 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 description coverage is only 43%, so the description must compensate and does not. It references 'motor yacht and catamaran', mapping to just two of the four vessel_category enum values, and says nothing about guests, budget_eur, charter_days, sub_id, or session_id.

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 the resource (luxury motor yacht and catamaran charters) which distinguishes it from the aviation and logistics siblings, but it supplies no verb at all. An agent cannot tell whether this searches, estimates, holds, or books a charter.

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 guidance, no mention of alternatives (e.g. geo360_vip_aviation_estimate, geo360_book_offer), and no exclusions. 'Strict coastal geographic verification' hints at a constraint but never states what qualifies or what happens when it fails.

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