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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful context by characterizing the data as pre-'collected' posts matched against a keyword and warning that non-lead items appear in results, but says nothing about pagination, defaults, or result volume for a 22-parameter listing tool.

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 front-loaded sentence with no filler; the scope clarification comes immediately after the core action. It is efficient, though its brevity is achieved by omitting content rather than by compressing it.

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?

For a tool with 22 parameters, zero schema descriptions, and no output schema, one sentence is far from sufficient. An agent cannot tell what the default result set looks like, how pagination behaves, or how the many filters combine, so significant guesswork remains before invocation.

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% across 22 parameters, so the description carries the full burden and delivers essentially nothing. Only the word 'keyword' loosely gestures at keywordId; filters like purpose, sentiment, favorites, needsResponse, scoreMin/Max, sources, platform, orders, and pageSize are entirely unexplained in both schema and description.

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 and resource: 'list collected posts that matched a keyword,' and adds a scope note that non-lead brand mentions are included. This partly separates it from the sibling list_leads tool, though the overlap is only implied rather than explicitly routed.

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?

There is no statement of when to use this instead of list_leads, get_brand_mentions_overview, or list_lead_keywords, all of which live in nearby name space. The clause 'including brand mentions that are not leads' hints at overlap but never says which tool to pick for leads versus mentions.

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