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

Annotations only give destructiveHint=true; the description adds substantial context: changes propagate to every channel with price sync enabled, affect live prices guests see, and are reversible only by re-setting prior values. It also notes a minimum stay alone requires an existing price, which is behavior not captured by the annotations or schema.

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?

Four compact sentences, each carrying distinct payload (effect, blast radius, reversal, per-operation requirement) with the live-price warning front-loaded. No filler or 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 mutation tool with minimal annotations and no output schema, the description covers consequence, reversibility, prerequisite read, and parameter invariants — everything needed to invoke it safely and 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 coverage is 100%, but the description adds a genuine cross-parameter constraint the schema does not enforce: each operation needs daily_price, min_length_of_stay, or both, and a minimum stay alone requires a pre-existing price. That is real semantic value beyond the field-level descriptions.

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) and resources (nightly price, minimum length of stay) scoped to dates on one or more properties. It names the sibling it pairs with (smoobu_get_rates) so an agent can separate it from the read-side tool without opening a 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?

Explicitly says to read current values with smoobu_get_rates first, and explains how to revert (set the old values again). The condition for using it — changing live prices pushed to channels — is stated directly, leaving nothing to inference.

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