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

With no annotations, the description carries the full behavioral burden and does so well: it discloses read-only semantics, the merge/derivation behavior across two sources, that unknown fields surface as TODO, and that no booking or payment card data is involved. It stops short of describing response shape or failure modes.

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 tight sentences, front-loaded with the read-only constraint and leading with the concrete return contents. The 'does not create a booking' clause is slightly redundant given the read-only opener, but it meaningfully pre-empts confusion with get_booking_link.

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?

No output schema exists, so the description must convey return content, and it enumerates the categories (details, room types, amenities, policies, check-in/out, pool season) plus the TODO edge case. Adequate for a no-arg read tool, though it could say more about how the merge resolves conflicts between Channex and lodge config.

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?

The tool takes zero parameters, so there is nothing for the description to clarify; baseline 4 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?

States a specific verb and resource ('Returns Portmans Motor Lodge property details and room types') and even names the data sources (Channex merged with lodge config). It implicitly separates itself from get_booking_link by stating it 'does not create a booking', though it never names a sibling tool explicitly.

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?

Usage is only implied: the read-only framing and the negative statements ('does not create a booking', 'does not accept payment card data') tell the agent what this tool is not for, but there is no explicit when-to-use guidance versus check_availability or get_booking_link.

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