apps__customer_review_summarizations__list

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description need not restate these. However, the description adds no additional behavioral context such as pagination behavior, response size limits, or what happens with missing filters. It only provides the HTTP endpoint, which is already implied by the resource.

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 a single, direct sentence followed by the endpoint. It is appropriately concise, front-loaded with the action, and contains no wasted words.

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?

The tool has 7 parameters and no output schema, so the description should help the agent understand what the response contains. It only states the resource, leaving the response structure to inference. However, the rich parameter schema and the list nature of the tool make it minimally sufficient for a simple list operation.

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?

The schema description coverage is 100%, so every parameter is already documented. The description itself adds no parameter-level meaning, which aligns with the baseline score of 3 when the schema carries the detail.

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 the tool lists customer review summarizations for an app, and the endpoint specifies the exact resource. It distinguishes from similar list tools (e.g., apps__customer_reviews__list) by explicitly naming the summarization resource, though it does not name alternatives.

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 gives no guidance on when to use this tool versus alternative list tools. It implies that an app ID is required but does not mention exclusions, alternatives, or typical use cases, especially given the many sibling list tools.

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