trmnl_list_room_booking_collection_screens

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

The annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the concrete API endpoint and sibling equivalence, but does not disclose auth needs, rate limits, pagination, or return behavior beyond the wording 'screens'.

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 short and front-loaded with the core action. The sibling comparison and endpoint are compact and useful, with no wasted filler.

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?

The tool is a simple read-only list operation and annotations cover its safety traits, but there is no output schema and the description does not describe return shape or pagination. The sibling comparison helps, but the definition is not fully self-contained for an agent that does not already know listRoomBookingCalendarScreens.

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 schema documents installation_id, collection id, and profile, and the description reinforces the path with the endpoint template. However, it does not explain the optional profile parameter or add meaning beyond the schema for the nested path arguments.

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 states a specific verb and resource: read the screens shown by a room booking collection. It also explicitly distinguishes this from the calendar-screens sibling by saying it is the same answer as listRoomBookingCalendarScreens, but for a collection.

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 clear context by comparing the tool to listRoomBookingCalendarScreens and clarifying that this variant is for collections. It does not explicitly list when not to use it or spell out prerequisites, but the intended use case is clear.

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