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

With only destructiveHint annotated, the description adds substantial behavioral context: it pushes to every channel with price sync enabled, changes live prices guests see, is reversible by re-setting old values, and requires an existing price for a minimum-stay-only change. This goes well beyond the annotation.

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?

Five tight sentences, front-loading the purpose, then side effects, reversibility/alternative, operation constraints, and API endpoint. Every sentence adds necessary information without repetition.

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 destructive nested-array mutation with no output schema and destructiveHint annotation, the description covers purpose, external side effects, reversibility, read-before-write guidance, parameter requirements, and the endpoint. Nothing critical for correct invocation appears 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 100%, so baseline is 3, but the description adds an important parameter constraint not in the schema: each operation needs daily_price, min_length_of_stay, or both, and a minimum stay alone requires an existing price. That meaningfully supplements the nested operations array.

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 (Set), resources (nightly price, minimum stay), and scope (dates on one or more properties), and explicitly names smoobu_get_rates as the read counterpart, so an agent can distinguish it from sibling rate and availability tools.

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?

Provides clear context for when the tool is used: modifying live guest-facing prices and minimum stays. It directs the agent to read current values first with smoobu_get_rates and notes the operation requirement, but does not enumerate explicit when-not-to-use or alternative update paths beyond that.

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