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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description usefully adds that results are cursor-paginated and that the payload includes private feedback and host responses, which is real behavioral context beyond the annotations. It stops short of noting filter combinations or ordering defaults.

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 sentences, zero filler. The returned-field list and the pagination trait are front-loaded immediately after the verb+resource, and the API endpoint citation is appended compactly.

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?

For a read-only, non-paginated-output list tool with annotations covering safety and no output schema, the description is sufficient: it names the scope, the pagination model and the returned fields. Minor gaps remain around default sort behavior and the relationship between the two scoping parameters.

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 63%: limit, cursor, lead_uid, property_uid and updated_since are documented in-schema, while sort, source and sort_direction enums are not. The description adds only the property/lead scoping and pagination hints, which map loosely onto parameters rather than explaining them, so it nets out to the schema baseline.

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 ('List guest reviews') and scopes it to a property or lead, plus enumerates the returned fields (rating, title, content, source, private feedback, host response). No sibling tool covers reviews, so no explicit differentiation is needed, but the definition never states how it relates to the get/list family around it.

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 closing line ('for a property or a lead') implies you must supply property_uid or lead_uid, and 'Cursor-paginated' implies iterating. There is no explicit when-to-use guidance, no statement that both scoping params are optional, and no exclusions relative to sibling list tools.

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