customer_reviews_get_instance

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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses nothing about read-only semantics, authentication, pagination, or the shape of the returned review. A bare route string conveys no behavioral context at all.

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?

The text is short but not concise in a useful sense: it is under-specified rather than economical, and it wastes its single line by duplicating the same route in parentheses instead of conveying 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?

A five-parameter tool with no annotations and no output schema needs the description to explain what is fetched and what comes back. The description provides none of that, leaving an agent with only the route string to work from.

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 each of the five parameters (id, include, fields_*) documented inline. Per the rubric, full schema coverage sets a baseline of 3; the description adds nothing beyond that baseline but does not degrade it.

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 is the raw HTTP route 'GET /v1/customerReviews/{id}' duplicated twice. It restates the resource and method already embedded in the tool name (customer_reviews_get_instance) without adding any distinguishing scope or framing, making it effectively a tautology.

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?

No when-to-use, when-not-to-use, or alternative is given. There are many sibling tools touching customer reviews (apps_customer_reviews_get_to_many_relationship, customer_reviews_response_get_to_one_related), and the description does nothing to route an agent between them.

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