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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the description's burden is lighter. It still adds real behavior: the returned offer is priced with the options the link advertised, which explains why the result may not match a fresh search. It says nothing about auth requirements or what happens with expired or malformed links.

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, front-loaded with the invocation trigger, then the return contract, then an example. Nothing is redundant with the schema or annotations, and no sentence could be cut without losing routing information.

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?

Even though an output schema exists, the description correctly summarizes the key return values and their purpose (chaining into get_offer). Combined with the annotation safety profile and full schema coverage for the single URL parameter, an agent has everything needed to call this 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?

With one parameter at 100% schema description coverage, the baseline is 3, and the description earns a bump by supplying a concrete example URL showing the query-string shape (offer_car, pickup_parking, pickup_at) that the schema only describes abstractly. The example is truncated, so it illustrates format rather than fully documenting the parameter.

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 names a specific trigger and resource: a beep.rent link to a single offer, including the forms it arrives in (e-mail, campaign, short beep.rent/r/ link). It also distinguishes itself from the downstream sibling by stating it returns search_id and offer_ref for get_offer, so an agent knows this is a link-decoding step, not a search or booking step.

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?

It gives an explicit trigger ('Use when the user pastes a beep.rent link') and names the follow-on tool (get_offer), which routes the agent correctly. It stops short of stating when not to use it, e.g. that pasted non-beep.rent URLs or plain offer searches belong to search_offers instead.

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