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

Annotations already declare readOnlyHint=true and destructiveHint=false; the description corroborates this and adds meaningful behavior: no reservation is made and the user completes booking on the package page. It also reveals the output shape, a deep link to /packages/{slug}, which goes beyond the structured fields.

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?

Three sentences with no filler: the core action is front-loaded, followed by package context, data source, and the key non-reservation caveat. Nothing is repeated from the schema, and 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?

This is a simple link-generator with full schema coverage and strong annotations. The description covers purpose, source of package identifiers, the either/or parameter selection, and the critical caveat that no reservation is made. An agent has everything needed to invoke 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 100%, so the baseline is 3. The description adds useful provenance by noting that package_id or slug come from search_packages and are alternative inputs, helping the agent choose between them. The remaining optional parameters are already well-documented in the schema.

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?

States a specific verb and resource: 'Generate a deep link to a curated Event Escapes PACKAGE detail page (/packages/{slug})'. This clearly distinguishes it from sibling tools like build_event_link and search_packages, and explicitly frames it as a link builder rather than a booking or search tool.

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?

Provides clear usage context: 'Takes a package_id or slug returned by search_packages', establishing input provenance and precedence. It also gives a strong when-not: 'This does not make a reservation: the user reviews ... and books on the package page.' It does not explicitly name alternatives like build_event_link, but the package-vs-event domain makes the intended use clear.

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