GET /room/booking/:id (Conexa Coworking > Booking)

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

Annotations already declare readOnlyHint=true and destructiveHint=false, aligning with the description's 'retrieval of data.' The description adds no behavioral details beyond this, but it does not contradict annotations. It could mention that no side effects occur, but given annotations, a score of 3 is appropriate.

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 a single sentence, making it concise and easy to digest. It is appropriately sized for a simple retrieval tool, though it could include more detail without being verbose.

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 lack of an output schema, the description should explain what data is retrieved, but it only says 'data from a room reservation.' This is vague. For a tool with low complexity and good annotations, more detail on the return value would improve completeness.

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 single parameter 'id' has a schema description that explains it as the value from the route. With 100% schema coverage, the description adds no additional meaning. The description does not elaborate on id format or constraints, so it meets the baseline but does not exceed it.

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 'Retrieval of data from a Room Reservation at Conexa' clearly states the verb (retrieval) and resource (room reservation), making the purpose obvious. It distinguishes from sibling tools like list_room_bookings, which list multiple bookings, by focusing on a single booking retrieval. However, it lacks specificity about what data is returned.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention that this tool retrieves a single booking by ID, while list_room_bookings lists many. The description offers no context about prerequisites or typical usage scenarios.

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