get_trending_terms

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

No annotations are provided, so the description carries the full burden of disclosing behavior. It only says 'returns' data and gives no details about rate limits, whether the call is read-only, possible empty results, or how full_data affects behavior. This is a minimal disclosure that does not sufficiently cover behavioral traits.

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 concise, front-loaded sentence with no filler. It communicates the core operation immediately and 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?

The tool is simple, has only two optional and well-documented parameters, and an output schema exists, so return shape is covered. However, the description lacks sibling differentiation and behavioral caveats, leaving an agent with enough to invoke it but not enough to confidently choose it among many similar trend tools.

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 schema already documents geo granularity and full_data. The description adds only the idea of a 'specific geo location', which aligns with the geo parameter but does not compensate for or add anything beyond the schema.

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 states a clear verb and resource: it returns Google trends for a specific geo location. However, it does not distinguish this tool from similarly named siblings like get_trends, get_top_trends, or get_ranked_trends, so an agent cannot easily tell why get_trending_terms is the right choice.

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 phrase 'for a specific geo location' implies this tool is for geo-scoped trend retrieval, but no explicit guidance is given about when to use it over alternatives like get_trends or get_trending_by_region. There are no when-not-to-use conditions or sibling references.

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