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

Annotations already declare readOnlyHint=true, so safety is covered; the description adds real behavioral value by disclosing the return ordering (most recent first) and the granularity of each entry. It does not mention pagination semantics despite limit/offset params, which keeps it from a 5.

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?

Two tight sentences with the core purpose and result shape front-loaded, followed by a short endpoint reference. Minor redundancy in the trailing API route, but nothing is bloated.

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 carries the burden of describing returns, and it does so adequately (field, old value, new value, timestamp, user, ordering). Pagination behavior goes unaddressed, which is the only notable gap for a read tool with limit/offset.

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% with all three parameters documented in the schema itself, so the baseline is 3. The description adds no extra meaning about reservationId, limit, or offset beyond what the schema provides.

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 resource (the audit trail for one reservation) with an exact description of what each record contains — field change, previous and new value, timestamp, actor. This clearly separates it from hostaway_get_reservation (current state) and hostaway_update_reservation (mutation) without needing to read either 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?

The phrase "Useful for 'who changed these dates / this price?'" gives a concrete triggering context, which is more than most siblings offer. It does not explicitly exclude or route against alternatives (e.g. use hostaway_get_reservation for current values), so it stops short of a 5.

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