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

Annotations already cover readOnly, idempotent, and non-destructive behavior, so no safety disclosure is needed. The description adds useful behavioral context by guaranteeing the ids are exact and by enumerating the fields they belong to, even though it does not detail the output structure.

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?

Two sentences with no redundancy. The core value proposition comes first, and the usage instruction is front-loaded in the second sentence.

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 zero-parameter, read-only lookup with no output schema, the description is complete: it says what is returned, which fields are covered, and when to call it. No relevant operational detail 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?

The tool has zero parameters and the schema is empty with 100% coverage, so there is no parameter documentation burden. The description adds value by naming the semantic dimensions (cities, who, style, vibes, pace, kosher, shabbatCity) that the returned vocabulary covers.

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 that the tool provides the exact ids plan_trip accepts for seven named dimensions, making its purpose concrete and unambiguous. It distinguishes itself from sibling content tools by explicitly tying it to plan_trip as a prerequisite lookup.

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 an explicit invocation instruction: 'Call this before plan_trip rather than guessing an id.' This tells the agent exactly when to use the tool and why, and implies that it is a helper rather than a standalone planning tool.

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