Brek — Direct Booking Finder

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive behavior, but the description adds crucial result semantics beyond that: 'found=false and urls=[]' is a successful result, an exhausted page can have found=true with empty urls, and no link found does not mean the listing is absent or has no booking site. It also limits scope to Airbnb listings only, giving the agent essential behavioral context.

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 dense but front-loads purpose and use cases before moving to result semantics and scope limits. Most sentences carry real value, though a few phrases (e.g., 'including questions about avoiding Airbnb fees' and repeating the 1–10 string constraint) are slightly redundant with the schema.

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?

Given the tool's lookup-and-pagination complexity, an existing output schema, and rich annotations, the description covers what an agent needs: what the tool returns, how to interpret empty results, how pagination works via next_offset, and what it explicitly does not do. Nothing essential is missing.

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 schema already documents all four parameters including limits, locale format, pagination offsets, and listing ID handling. The description repeats '1–10 Airbnb room URLs or exact listing IDs as strings' but adds no new meaning about limit, locale, or offset beyond what the schema provides, making the baseline 3 appropriate.

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 opens with a specific verb and resource: 'Look up mapped property manager or operator booking links for the same vacation rental listed on Airbnb.' It then enumerates concrete user intents, so an agent knows exactly what this tool does without needing to infer from the name.

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 names multiple triggering scenarios (book directly, find the manager website, explore cheaper options, avoid fees) and explicitly lists out-of-scope requests (does not search destinations, compare prices, check availability, guarantee savings, or make reservations). With no sibling tools, it still defines the boundary of when this tool applies.

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