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

Annotations already declare readOnly, openWorld, and non-destructive, so the safety profile is covered. The description adds meaningful context beyond that: history expands monthly trend points, labels rows with snapshot age, and discloses that ingestion is intentionally paused so history never claims to be current. That paused-source caveat is exactly the kind of behavioral nuance structured fields cannot convey.

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?

Front-loads the core purpose and then the two view modes in four tight sentences with little waste. The final sentence about paused ingestion is slightly repetitive given the earlier mention of 'paused-source history status' but is defensible as it clarifies expectations.

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?

An output schema exists, so return-value detail is not required. The description covers mode selection, the freshness/paused caveat, and history row labeling, which is sufficient for correct invocation of a read-only tool.

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%, so the baseline is 3. The description reinforces the live/history split for the view param, but does not add syntax, defaults, or constraints beyond what the schema already documents for limit, offset, dates, or the include_* flags.

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?

States a specific verb and resource ('Show Amazon Customer Feedback review-topic trends') and scopes it to a child ASIN. This distinguishes it cleanly from siblings like get_product_reviews or get_brand_health without needing to open a schema.

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?

Explicitly explains the two operating modes: view=live for the current six-month Amazon response and view=history for stored snapshots, including the default. This is strong when-to-use guidance for the main behavioral fork, though it offers no cross-sibling routing (e.g. vs get_product_reviews).

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