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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely non-obvious behavior: derived rates cannot be set manually ('SiteMinder does not let you set derived rates by hand') and the auth requirement ('Needs the user's Cotlet API key with access to this app'). It omits pagination/volume behavior, keeping it from a 5.

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?

Front-loaded and reasonably sized, but the second sentence ('Returns every room type with its room rates') largely restates the first, so not every sentence fully 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?

With no output schema, the description must convey the return shape, and it does: every room type with its rates, derived rates plus their base rate, and channel mappings. It also states the auth prerequisite. Adequate, though pagination/scope limits are unaddressed.

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 the schema cannot carry semantics and the baseline is 4. The description does not discuss parameters, which is acceptable here since there are none.

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 ('List room rates') and details the payload: room types, their rates, derived rates, and channel mappings. It is distinguishable from write siblings like siteminder_update_rates, though it does not explicitly contrast itself with read siblings such as siteminder_get_inventory or siteminder_get_rate_parity.

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?

Gives downstream guidance ('Use the IDs from here in get_inventory and the update tools') which implies the workflow context, but offers no explicit when-to-use versus the other SiteMinder read tools (get_inventory, get_rate_parity). Usage is implied rather than stated.

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