Individual user reviews

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

Annotations cover the safety profile (readOnlyHint, openWorldHint), so the bar is lower, and the description still adds a real behavioral fact: the API's large parsed_content token dump is stripped from the returned rows. It also flags that the filter vocabularies are not enumerable from the contract. It doesn't mention pagination or result-size behavior, keeping it below 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 sentences, no filler, with the payload description front-loaded and the field-drop caveat following. The second sentence packs filtering guidance and the reference pointer densely but every clause carries information.

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 15-parameter, no-output-schema tool with only light annotations, the description covers the important output caveat and the filter vocabulary dependency but omits pagination semantics for page/limit and gives no sense of result volume. Adequate to call correctly, incomplete for callers who need to page or budget tokens.

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 60%, so several parameters (page, end_date, versions, search_term, app_id) rely on name alone. The description adds meaningful context for the filter params (tags, sentiments, rating_filter) by pointing to sensortower_reference for allowed values, but does not compensate for the undocumented remainder.

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 the resource and its per-review contents (rating, sentiment, tags, version, language), which is specific enough to separate it from aggregate siblings like sensortower_review_breakdown and sensortower_ratings. It stops short of an explicit 'returns individual user review rows' framing, but the scope is unambiguous.

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?

It tells the agent how to narrow results (tags/sentiments/rating_filters) and routes vocabulary lookups to sensortower_reference, which is useful. It never states when to choose this over the aggregate review siblings, so the routing guidance is only partial.

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