hostkit_get_reservation_by_cm_id

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

With no annotations, the description only states it gets a reservation, but does not disclose behavior on missing reservations, error conditions, or authentication needs. It is adequate for a simple read operation.

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 with 12 words, no fluff, and front-loads the action. Every word earns its place.

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 simplicity (2 params, no output schema), the description is sufficient for a basic lookup but does not describe return values or potential limitations. Largely complete for its complexity.

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 input schema covers both parameters with descriptions (100% coverage), and the description merely repeats 'channel manager name' and 'reservation ID' without adding further details. Baseline score of 3 is 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 uses a specific verb 'Get' and resource 'reservation', and uniquely identifies it by 'channel manager name and reservation ID', distinguishing it from siblings like 'get_reservation' and 'get_reservations'.

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 implies usage when a channel manager name and reservation ID are known, but does not explicitly state when not to use it, nor does it mention alternative tools like 'get_reservation' for internal IDs.

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