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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety/scope profile is covered. The description adds freshness context ('currently') but says nothing about rate limits, caching, or region/locale dependence. Moderate added value over structured fields.

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 single compact sentence stating what it returns and where the result goes next, with the resource front-loaded. No filler.

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 documentation is unnecessary, and there are no parameters to explain. The description is complete for a parameterless read tool, with only minor room to note the trending feed's volatility or regional scope.

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?

Zero parameters, so there is no schema semantics for the description to complement. Baseline 4 applies; the description correctly indicates no input is required.

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 resource (GOAT trending/popular search terms) with an implied read verb and clearly distinguishes itself from goat_suggest by noting the terms are 'currently surfacing as popular.' An agent can tell this apart from the other goat_* endpoints.

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?

'ready to pass to goat_search' explicitly describes the downstream workflow, which tells the agent how to use the output. It stops short of stating when-not to use it or naming alternative discovery tools like goat_suggest or goat_search_facets.

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