trmnl_get_room_booking_settings

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the description does not need to restate the safety profile. It adds the HTTP endpoint path but says nothing about authentication, rate limits, or what the returned settings include, leaving some behavioral context uncovered.

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?

Very short and front-loaded: the first sentence states the purpose immediately, and the endpoint line adds a useful implementation hint without bloat. Nothing extraneous is present.

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?

For a simple read-only GET with rich annotations and only two parameters, the definition is minimally adequate. Because there is no output schema, the description could have said what settings are returned, which would materially help an agent decide whether to call it.

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?

Both parameters already carry descriptions in the schema (installation_id and profile), and the description adds no further meaning about them. With only 50% schema description coverage, the description should compensate by explaining the nested path parameter or the profile semantics, but it does not.

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 ('Read') and resource ('settings of a room booking installation'), making the read-only nature obvious and separating it from the sibling update_room_booking_settings. However, it never names that sibling or any other alternative, so differentiation is left implicit.

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 verb 'Read' and the GET endpoint imply that this is the retrieval counterpart to the update tool, but the description gives no explicit when-to-use guidance, prerequisites, or alternatives. Usage is inferable rather than stated.

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