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

Annotations only provide destructiveHint=true; the description adds value by disclosing it is a mutation ('MUTATES OwnerRez data'), the underlying POST /v2/bookings JSON write, and that it returns the created booking. It does not discuss auth requirements or failure/partial-write behavior, but the additions exceed the annotation content.

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?

Front-loads the critical fact ('MUTATES OwnerRez data') and packs verb, endpoint, object semantics, the `fields` rationale, and return value into four tight sentences with no filler.

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 output schema, the description usefully states it 'Returns the created booking,' and it covers the mutation, endpoint, and object semantics for an 8-param tool. It is largely complete, though auth/permission expectations for the write are unaddressed.

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 the baseline would be 3, but the description adds meaning beyond the schema by explaining why `fields` exists ('the exact charge/quote shape is account-specific') and that it is merged with typed fields. This contextualizes the flexible-object parameter rather than merely restating it.

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 and resource ('creates a new booking (reservation)') and clarifies the domain object relation ('ties a guest to a property for a date range'). Distinguishes it from siblings like create_quote and create_guest, which also create records but of different types.

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?

Gives implied usage: it is the tool to create a booking, and it advises passing account-specific documented fields via `fields`. However, it never names alternatives (e.g. create_quote for pricing) or when-not conditions, so routing guidance is only inferred.

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