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

No annotations are provided, so the description carries full responsibility. It discloses non-obvious behavior: best-price logic, weekend surcharge (+30%), catering flat rates, and personalization via API token (company pass or individual discount). This adds value beyond the 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?

The description is a single paragraph of moderate length with front-loaded key information. It is efficient and avoids redundancy, though a more structured layout (e.g., bullet points) could improve scanability.

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?

Given 8 parameters, no output schema, and no annotations, the description provides sufficient context: it lists input sources (list_rooms, list_services), explains pricing logic, and mentions authentication/profiling. It is complete enough for an agent to invoke the tool without additional explanation.

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% with descriptions for each parameter, but the description adds relational context: room IDs come from list_rooms, service IDs from list_services, and that 'participants' is required for per-person catering (though schema allows null). This additional meaning helps the agent use parameters correctly.

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 clearly states the tool calculates an informal total price using the real pricing engine, including best-price logic, weekend surcharge, and catering flat rates. It differentiates from list_rooms by advising against manual calculation, making purpose specific and distinct from siblings.

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 explicitly says to use this tool instead of manually calculating prices from list_rooms, and specifies that room IDs come from list_rooms and service IDs from list_services. While it lacks explicit when-not-to-use scenarios, the guidance is clear and action-oriented.

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