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

Annotations already declare readOnlyHint and openWorldHint, so the description need not restate safety. It adds behavioral context by listing the exact types of information returned (airline, dates, steps, caveats, transfer options), giving the agent a clear expectation of the response content.

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?

One concise sentence, front-loaded with the main purpose ('full detail') followed by a compact list of content areas. No redundancy or filler words; every word 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 simple lookup tool with a single parameter, the description outlines both the input (slug) and the output categories, enabling the agent to anticipate the result structure. Annotations cover safety and world assumptions. Missing an explicit mention of not-found behavior is a minor gap, but overall the description is complete enough.

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?

With 0% schema description coverage, the description compensates by stating that the slug identifies a specific posted deal. For a single required string parameter, this is adequate semantics, though it could be improved by noting where the slug comes from (e.g., from list_live_deals).

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 uses the specific verb 'get' and resource 'deal', clearly scoped to a single posted deal identified by slug. It distinguishes from sibling list_live_deals by emphasizing singular detail and enumerating the content (booking airline, dates, steps, caveats, transfer options).

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 clearly implies when to use this tool: when you need full details for a specific deal identified by a slug. It does not explicitly compare to alternatives or state exclusions, but the context of a single deal versus listing is sufficient for basic usage differentiation.

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