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

Annotations already cover readOnly, idempotent, non-destructive, closed-world behavior. The description adds genuinely new behavioral context: the observations are 'moderated' (pre-filtered content) and the tool neither collects nor submits reviews, which tells the agent this is a read-only, content-curated source rather than a live review pipeline.

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?

A single front-loaded sentence delivering the action, the resource, and the scope boundary with no filler. It is arguably too terse for the amount of information an agent still needs, but nothing is wasted.

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 should say more about what an 'observation' is and what comes back (text, rating, attribution, count). Annotations carry the safety profile, but return shape and the meaning of the preference filter are left entirely unexplained.

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 0% for two parameters, and the description says nothing about the 'preference' filter or how 'property_id' scopes results. The enum values are self-descriptive, which partially mitigates the gap, but the description does not compensate for the missing documentation as low coverage requires.

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 ('Read') and resource ('moderated guest observations'), and contrasts it with 'property facts', which effectively separates it from the sibling get_customer_property. It does not explicitly name that sibling, so the differentiation is implied rather than declared.

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 clause 'separately from property facts; no review collection or submission' sets a boundary and implies property-fact queries belong elsewhere, but it never states positively when to call this tool or names the alternative tool to use for facts. Usage is inferable but not spelled out.

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