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

No annotations exist, so the description carries the full behavioral burden. It usefully discloses the exact tax and gratuity rates applied and that LET is conditional, but never states that this is a pure side-effect-free computation, that 'venue fee' is an unspecified/assumed input, or how the total is presented (per person vs. table total).

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?

One dense sentence that front-loads the outcome and then lists the cost components; there is no filler or restatement of the tool name.

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?

With no annotations and no output schema, the description should clarify the return shape (per-guest vs. total spend) and how the unspecified venue fee is determined. The rate breakdown is helpful but leaves those gaps for a calculation tool whose output consumers must interpret.

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 all three parameters are already documented, including the LET boolean and its club-vs-dining semantics. The description's mention of the 9.0% LET and 20% gratuity reinforces the parameters but adds no new syntax or constraints beyond the schema.

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 (calculate) and a precisely-scoped resource (out-the-door Las Vegas VIP table cost), and enumerates exactly which cost components are included. It is unmistakably distinct from the venue-search and venue-detail 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 intent to convert a quoted pre-tax minimum into a true total is implied by 'true out-the-door' cost, but there is no explicit statement of when to call this rather than get_venue_details, and no stated prerequisites or exclusions. Usage is inferable but not guided.

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