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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context the annotations lack: a per-call price of $0.006 and the conditional behavior that imports are only included when hs is supplied. It says nothing about response shape, section omission when data is missing, or latency.

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?

Two short sentences with the source list front-loaded, but the second sentence repeats the same three components almost verbatim, so roughly a third of the text is redundant filler rather than new 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?

For a three-source composite with no output schema, the description does tell the agent which sections come back, which is the essential missing piece. It still leaves the agent guessing about response structure, behavior when hs is omitted, and the meaning of lang, which matters at 0% schema coverage.

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 0%, so the description must carry parameter meaning and only partly does. '(with hs)' explains that hs gates the U.S. imports section and 'for a product' implies q, but the lang parameter is never mentioned and no format hints (e.g., HS code length, language codes) are given for any of the three.

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 names a concrete composite resource (a product research brief) and enumerates its three components: Wikipedia interest trend, CPSC recalls, and U.S. imports. This distinguishes it from single-source siblings like product_recalls, import_trends, and topic_demand, though 'interest trend' stays vague about the underlying metric.

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?

It says to use this 'for a one-call product research brief,' which implies the alternative (calling the three source tools separately) without naming any sibling. The second sentence largely restates the first, so the when-to-use guidance is present but circular and has no exclusions.

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