trend_details

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

Annotations already declare readOnly/idempotent/openWorld/destructive=false, so safety is covered. The description adds real value beyond them: with_chart triggers 'two more requests,' disclosing a cost/latency trait, and geo blank resolves to a default location. That is meaningful behavioral context the structured fields do not carry.

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?

A front-loaded summary sentence followed by short per-parameter clarifications; nothing is padded. The parameter notes are compact and each earns its place.

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 values need not be explained, and the headline purpose is captured. But with news and hours undocumented and no routing guidance among the dense sibling set, the definition is not fully complete for a 5-parameter 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 coverage is 0%, so the description must compensate. It documents trend, geo, and with_chart semantics well, but the news (default 5) and hours (default 48) parameters get no explanation at all, leaving two of five parameters opaque.

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-driven scope: fetching every query, news, and hourly curve for 'one current trend.' This pins down the resource clearly, though it does not explicitly name a sibling (e.g. snapshot_trending or trend_momentum) to disambiguate among the many trend_* tools.

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?

'one current trend' implies context, and the geo: blank default note hints at usage, but there is no explicit when-to-use vs alternatives guidance despite a crowded sibling set (interest_over_time, daily_history, trending_now, etc.). Usage is inferable but not stated.

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