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

Annotations already declare the read-only, non-destructive, open-world profile, and the description goes beyond them by disclosing default ordering (newest first), the effect of the sort parameter, and an authentication prerequisite (Cotlet API key with access to this app). It does not mention pagination ceilings, but the limit parameter in the schema largely covers that.

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?

It is short and front-loaded, leading with what the tool returns and following with sorting and auth notes. The phrase 'with rating, date and text' is repeated verbatim, which is minor redundancy but keeps it readable.

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 correctly describes return contents and ordering, and it covers the auth requirement. Combined with a fully documented three-parameter schema, an agent has what it needs; only pagination/return-volume behavior is left implicit.

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 the schema already documents activity_id, sort, and limit; that sets the baseline at 3. The description adds only outcome-level meaning for sort ('rating to see the best rated first'), which is a marginal gain over the enum values already listed.

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 names a specific verb and resource — traveler reviews of a single activity — and enumerates the returned fields (rating, date, text). It does not explicitly differentiate itself from nearby siblings like klook_get_activity, which an agent might assume also surfaces ratings, so it is clear but not sibling-aware.

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?

'Use it to check what travelers say before you book' gives a concrete decision context for calling the tool. It stops short of naming an alternative or stating when not to use it (e.g., versus fetching an activity's aggregate rating), so no explicit routing guidance is provided.

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