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

Annotations already declare readOnly, idempotent, non-destructive, openWorld, so the safety profile is covered. The description adds genuine context beyond them — the 4h/12h reporting windows and what passing "none" for country_pid does — but says nothing about pagination behavior, result volume, or how windows are represented in the returned rows.

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?

Three short clauses, no filler, and the read tag plus the core enumeration are front-loaded. Every sentence conveys a distinct constraint rather than restating the name.

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?

With 0% schema description coverage, six optional parameters, and no output schema, the description should resolve the ambiguities an agent cannot resolve elsewhere. It leaves the country_uid vs country_pid relationship, the default page size, and the meaning of created_date entirely unaddressed, which is enough to cause a mis-call.

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 the full burden, and it explains only two of six parameters: `keyword` (matches a trend name in either window) and `country_pid` (child region id; "none" keeps only country-level rows). The distinction between `country_pid` and `country_uid`, plus `page`, `per_page`, and `created_date`, remain completely undocumented.

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 gives a specific verb+resource ("List X/Twitter trends") and adds scoping detail (4h / 12h windows, per country). The platform qualifier 'X/Twitter' implicitly separates it from the TikTok/Instagram/YouTube trend siblings, but it never names an alternative explicitly, so differentiation is inferential rather than stated.

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?

Usage is only implied by the description of the country and keyword filters — an agent can infer this is the way to browse trends for a region or to look one up by name. There is no when-to-use / when-not guidance and no pointer to sibling tools such as list_tt_trends or search_ig_trends for other platforms.

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