ghl_product_review_count

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

The description adds value beyond annotations by specifying the HTTP endpoint, version header, and OAuth scopes (products.readonly). However, it does not describe the response format (e.g., returns an integer count) despite no output schema, leaving a gap in behavioral understanding.

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 description is short and includes endpoint/auth scopes, but it repeats 'Fetch Review Count as per status' twice, which is unnecessary. Otherwise, minimal waste.

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?

Given the tool has 7 parameters (2 required), no output schema, and siblings like ghl_product_review_list, the description lacks contextual completeness. It does not differentiate from sibling tools, explain the response, or cover all parameter purposes implicitly.

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?

With 86% schema description coverage, the baseline is 3, but the description does not add meaning to parameters. Instead, it mentions filtering 'as per status' which is not present as a parameter, potentially misleading. No parameter-specific details beyond 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 description clearly states that the tool fetches a review count, specifying the resource and verb. However, the phrase 'as per status' is not directly reflected in the input schema parameters (which include rating, dates, IDs but no status field), causing slight ambiguity.

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 description provides no guidance on when to use this tool versus alternatives like ghl_product_review_list or ghl_product_review_get. No usage context or exclusions are given.

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