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

The description discloses that the tool only generates a link and does not perform a reservation, which is beyond the annotations' read-only/idempotent hints. It also notes the tool is for curated packages and emphasizes user interaction on the package page. While annotations already cover safety, the description adds clarity about the tool's non-reservation behavior and its role in the user flow.

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 three sentences long and front-loaded with the action and resource. It earns every sentence by providing purpose, usage context, and a clear limitation, with no fluff or repetition of schema details.

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?

The tool is simple (generates a link) and the description covers its purpose, when to use it, and what it does not do. Annotations cover safety, and all parameters are documented in the schema. No output schema is needed because the output is self-evident. The description is complete for guiding an agent.

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 covers 100% of parameters with descriptions, so the baseline is 3. The description adds minimal parameter-specific meaning beyond stating it surfaces a package; it does not explain parameter formats or constraints. However, it reinforces that parameters come from search_packages results, which is useful context but not required because schema already documents each field.

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 the tool's function: 'Generate a deep link to a curated Event Escapes PACKAGE detail page'. It specifies the resource (package detail page) and the action (generate deep link), and differentiates from siblings by focusing on packages and explicitly referring to search_packages. The phrase 'does NOT make a reservation' further clarifies its non-booking role.

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 explicit usage context: 'Use this AFTER calling search_packages to surface a specific package to the user.' It also states when not to use it: 'This does NOT make a reservation - the user reviews tier/duration/guest selectors and books on the package page.' This clearly directs the agent to use it only after search, and not as a booking action.

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