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

With no annotations, the description carries the transparency burden. It discloses what the list contains (name, description, validity period) and importantly states that prices are not included because they depend on stay and party, directing the agent to get_stay_price. It does not explicitly state read-only behavior or pagination/error behavior, but for a simple listing tool this is reasonable coverage.

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 filler. The first sentence front-loads the purpose and content; the second adds a valuable workflow note about using get_stay_price. Every sentence earns its place.

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 one-parameter tool with no output schema, the description adequately explains what is returned, the scope, and the critical exception that prices must be requested separately. Minor missing details such as exact return shape or pagination are not significant for this simple list operation.

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 schema fully documents the sole parameter 'domain' as a location slug with an example, giving 100% coverage. The description only reinforces this with 'one location' and does not add additional parameter syntax, format constraints, or examples beyond what the schema already provides.

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?

Description clearly states the resource: 'bookable packages of one location: stay arrangements and add-on extras, with name, description and validity period.' It distinguishes itself from the pricing sibling by directing price requests to get_stay_price, and its focus on packages/add-ons separates it from list_accommodation_types.

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 clear context for when to use the tool: to get the bookable packages of a single location. It also instructs the agent to follow up with get_stay_price using the packageId when a price is needed. It lacks explicit exclusions for other sibling tools, so it misses a full 5.

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