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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so safety is covered. The description adds genuinely non-obvious context: that each item carries a decision brief plus evidence, and the important caveat that the confidence score measures evidence completeness rather than probability of success. It still omits ordering and pagination behavior.

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 sentences, each load-bearing: scope, return-content semantics, and a precondition. The caveat about the confidence score is front-loaded where an agent will read it before interpreting results.

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 no output schema, the description usefully characterizes what comes back (recommendations with decision briefs, evidence, and a confidence score) and the precondition for calling. Minor gaps remain around default status filtering and result ordering, but nothing essential to correct invocation is missing.

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 only 40%: limit and match_user_interests carry descriptions, while status and priority have none. The description partially compensates by enumerating recommendation categories that map to the recommendation_type enum, but it says nothing about status, priority, or default filtering behavior.

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 ("List") and a specific resource ("recommendations TrendsAGI generated for this account") and enumerates the concrete types returned (marketing angles, content ideas, SEO actions, PR responses). This cleanly distinguishes it from siblings like list_trends, list_crisis_events, and search_trend_insights.

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?

Provides one real gating condition — "Requires a plan with recommendations" — which tells the agent when the call is even valid. However, it never states when to prefer this over adjacent tools such as search_trend_insights or get_trend_ai_insights, so the routing guidance is only implied.

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