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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that all queries are parameterized and scoped to the current project, and that supplying contentIds swaps filter-based sampling for a point lookup. It says nothing about cost/latency characteristics or result shape beyond the per-operation labels, so the added behavioral value is modest.

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?

Front-loaded with the scope sentence, followed by an operation menu where each entry carries its return shape. The enumeration is long but each clause is load-bearing; only the trailing skill-load instruction could arguably move to the front.

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 14 parameters, 6 operations and no output schema, the description does real work by sketching what each operation returns (totals, per-topic split, trend series, sample messages). Pagination and the exact response envelope are unaddressed, but per-operation caps are documented in the schema.

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 100%, so the baseline is a 3; the description earns above that by consolidating the operation-to-parameter contract in one place — 'phrases ... use phraseColumn=hates for complaints', '[phrases] requires phraseColumn', '[breakdown] requires dimension'. That cross-field dependency reasoning is the main thing an agent gets wrong on a 14-parameter dispatcher, and it is surfaced clearly.

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 — 'Run analytical queries over the community pulse (player sentiment) data' — then enumerates all six operations with their output shapes. It is clearly distinguishable from get_community_pulse (which yields quoteContentIds) and list_sentiment_sources (which yields source ids).

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?

Gives a concrete prerequisite ('Load the understand-community-pulse skill ... first') and names sibling touchpoints (get_community_pulse for contentIds, list_sentiment_sources for ids). It does not, however, explicitly say when to reach for get_community_pulse instead of this tool, so the alternative routing is only implicit.

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