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

Goes well beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true) by disclosing that changes go live on mapped channels, that updates take a few minutes, that it requires a per-call confirmation by default, that the Cotlet API key must have app access, and that it reaches other people. This is exactly the mutation side-effect and auth context an agent needs.

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 with the core action, then layers caveats and operational constraints in short, discrete sentences. It is dense and slightly long, but every sentence contributes a distinct behavioral fact rather than restating the schema.

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 6-parameter mutation tool with no output schema, the description covers side effects, propagation timing, overwrite risk from external systems, confirmation behavior, and auth requirements. Nothing an agent needs to invoke it safely is missing.

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?

Schema coverage is already 100%, so the baseline is 3, but the description adds real meaning: it explains that a single nightly rate is applied to all listed room rates and that channel targeting defaults to all mapped channels. It clarifies the semantics of how 'rate' and 'channels' interact across the date range beyond the per-property schema lines.

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: 'Set the rate for room rates or channel rates over a date range.' This clearly distinguishes it from sibling mutation tools like siteminder_update_availability and siteminder_update_restrictions, and an agent can tell what it changes without opening the schema.

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 strong applicability context: derived rates cannot be set, channels only update within their maximum update period, and two-way PMS/RMS/CRS systems will overwrite the change. It stops short of naming an explicit alternative tool (e.g., checking parity or listing room rates first), so it is clear context without full when-not/alternatives routing.

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