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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It mentions the need for a bearer token (authentication) and implies a read-only list operation, but does not explain whether this returns full itinerary objects or summaries, whether it has pagination or limits, or any rate limits. For a listing tool with no annotations, this is insufficient transparency.

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 a single, front-loaded sentence that conveys the purpose, scope, ordering, and authentication requirement. Every element earns its place, with no wasted words. It is optimally concise for the information it provides.

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 tool with 0 parameters, no output schema, and no annotations, the description is minimally adequate. It covers the basic purpose and an important requirement (bearer token). However, it does not describe the output format or any limits (e.g., pagination, max results), leaving the agent uncertain about how to process the response. Given the tool's low complexity, a score of 3 is appropriate – complete enough for basic use but lacking expected details.

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 has zero parameters, and the schema description coverage is 100% (since there are no params to document). Per the instructions, '0 params = baseline 4' but the baseline is reduced because the description does not add value beyond the schema (which is already empty). The description implies a full list without filters, which is clear, but no additional semantic richness is added. A score of 3 balances the baseline of 4 with lack of added context.

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 clearly states what the tool does (list itineraries) and specifies the source ('created by the Iconic Expeditions concierge') and ordering ('most recent first'). It distinguishes itself from other list/get tools by adding the scope 'concierge-created' and the sort order. A score of 5 is not given because it does not explicitly differentiate from siblings like 'list_destinations' or 'get_itinerary' by naming them.

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 provides no guidance on when to use this tool versus alternatives (e.g., get_itinerary or search tools), nor does it mention any exclusions or preconditions beyond the bearer token. With 22 sibling tools covering related operations, this is a significant omission for an AI agent to make a correct selection.

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