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

With zero annotations the description carries the full burden, and it does disclose real quirks: the default aggregates only active project platforms, totals cover every platform in the window, timeSeries silently omits sub-daily-cadence platforms (e.g. weekly Claude/Grok) unless they are the only ones requested, and platformCadences can be null. It stops short of permissions or error behavior, but the output/aggregation gotchas are genuinely useful.

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?

Purpose is front-loaded in the first sentence and every subsequent clause carries information rather than filler. The second half is dense and jargon-heavy (shareOfVoice, primaryShareOfAllCitations, platformCadences), but it is compact for the amount of return-shape detail conveyed.

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?

There is no output schema, so the description usefully explains what each returned series/metric includes and when platforms are omitted from timeSeries. Combined with the fully-documented parameter schema, an agent has enough to call and interpret the tool, though which parameters select which metric is left implicit.

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 all five parameters are already documented and the baseline is 3. The description adds little parameter-specific detail beyond hinting that inactive platforms are excluded by default (relevant to includeHistoricalPlatforms), without clarifying windowDays/grouping interactions.

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 ('Get competitive positioning data') plus the data scope (primary, competitor, other citations), so the agent knows what it returns. However, it never differentiates itself from the closely-named sibling devtune_get_positioning or from citation tools like get_citation_stats, leaving sibling disambiguation to inference.

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 description explains what the metrics mean but never says when to call this tool versus alternatives such as get_positioning or get_citation_analysis. There is no explicit when/when-not guidance; the closest thing is a default-behavior note about active platforms, which is behavioral rather than selection guidance.

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