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

With no annotations provided, the description carries the full burden. It adds behavioral context by specifying that the calculation includes seasonal rates, discounts, nights, and persons, which goes beyond the raw input/output schema. However, it does not disclose whether the operation is read-only, what the return format looks like, or how errors are handled.

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?

The description is a single, front-loaded sentence that communicates the tool's purpose and scope without any redundant words. Every phrase 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?

While the description covers the core purpose and calculation factors, it lacks details about return values, edge cases, or prerequisites. Since there is no output schema and no annotations, the description should provide more context about expected behavior, leaving it adequate but with clear gaps.

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 schema provides 100% coverage of parameters, so the baseline is 3. The description adds value by linking dates to 'número de noches' and referencing 'personas', and by explaining that discounts and seasonal rates are factored in, enriching the semantic meaning of the inputs.

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?

The description starts with a specific verb 'Calcula' and resource 'precio total de una estancia', clearly distinguishing it from sibling tools that list or search properties. It also lists the key factors (seasonal rates, discounts, nights, persons) that define its scope.

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?

The description implies usage for calculating stay prices but provides no explicit when-to-use or when-not-to-use guidance. There are no alternatives mentioned or exclusions given, leaving the usage context purely implied.

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