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

Goes well beyond the annotations (which only flag a non-destructive, open-world mutation). It discloses channel propagation timing, that derived rates are returned in 'skipped', that sub-minimum rates silently fail, that per-call confirmation is on by default, and that a Cotlet API key with app access is required. That is exactly the behavioral context annotations cannot carry.

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, but the first and third sentences restate the same action ('Set the base rate of room rates over a date range' vs 'Sets the base rate of one or more room rates over a date range'), and 'like Bulk Update' appears twice. Several sentences overlap, diluting an otherwise informative block.

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 mutation tool with no output schema, it covers outcomes well: what propagates to channels, what gets skipped, what fails silently, and the auth requirement. The main gap is that it never explains how the 'skipped' result is surfaced to the caller, but overall it is sufficient to invoke correctly.

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 description coverage is 100%, so every parameter is already documented in the schema. The description's only additions are that weekdays are optional and that rate must clear the property minimum, which is useful but marginal. Baseline 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?

States a specific verb and resource: 'Set the base rate of room rates over a date range', with scope details (date range, optional weekdays, multiple rates). It implicitly separates itself from rate-restriction/inventory siblings by focusing on base rate, but never names an alternative tool, so it falls just short of 5.

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 real when-to-use context: derived rates cannot be edited, a rate below the property minimum will not save, and confirmation is required per call by default. It lacks explicit routing to alternatives (e.g. update_restrictions), so it is clear context without being a full decision guide.

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