customer_review_responses_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, and it discloses nothing: not whether the call is safe/read-only, what it returns, how errors or missing ids behave, or what include/fields expansion does. A route string alone is not behavioral disclosure.

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, but the content is literally duplicated in parentheses, which is pure waste. Brevity here comes from under-specification rather than disciplined editing, and there is no usable front-loaded statement of purpose.

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 GET-instance tool with four parameters, no output schema, and zero annotations, the agent needs at least what resource is fetched and what the response looks like. The description supplies none of that, relying entirely on the schema and tool name.

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% (all four parameters, including include and the two fields_* filters, are documented in-schema), so the baseline of 3 applies. The description adds no syntax or format information beyond the schema.

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 text is a bare HTTP route, "GET /v1/customerReviewResponses/{id}", repeated verbatim in parentheses. It signals a read of a single customerReviewResponses resource, but conveys no purpose beyond the tool name and gives no sibling differentiation against the many other get_instance tools.

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 guidance, no mention of alternatives such as customer_reviews_get_instance or the get_to_one_relationship variant, and no prerequisites for the id argument. The only hint is the conventional GET semantics.

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