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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety is covered; the description adds real behavior beyond them: results are ordered best-first, pre-filtered to offers that fit, and the offer_id prefix determines whether booking happens off-site via tracked_url with no sign-in or on Arugula. That is meaningful operational context an agent would otherwise have to guess.

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?

Front-loaded with the core what and ordering, then offer_id semantics. Dense but every sentence carries signal except the terms/privacy boilerplate, which is presumably mandatory but still occupies space.

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?

With no output schema, the description does the work of describing the return payload (tracked_url, how_to_buy, offer_id prefixes) and its ordering. It leaves open edge cases such as what is returned when nothing fits, but the essentials for correct invocation are present.

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 coverage is 100% and both parameters are self-describing, so the schema already carries the load. The description restates the intent_id provenance but adds nothing about the `brief` flag beyond what the schema says, so baseline 3 applies.

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?

Specific verb+resource: retrieves offers ranked for an intent, best first, restricted to those that fit, each with tracked_url and how_to_buy. It also decodes the offer_id prefixes, which distinguishes the two offer types, and ties the tool back to find_offers so its role in the pair is unambiguous.

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 phrase 'from find_offers' plus the intent_id schema note make the correct upstream call explicit, and the offer_id prefix explanation tells the agent what to do next (open tracked_url for lst_, no sign-in; off_ offers are on Arugula). It stops short of stating when not to call it (e.g. before find_offers has run, or when offers don't fit), so it isn't a full when/when-not/alternatives statement.

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