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 nothing beyond that — no note on pagination behavior, result volume, or what 'tracked' means in terms of scope.

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?

It is a single short sentence, but 'This tool is used to' is pure filler and the 'and/or' hedge makes the scope less clear rather than more. Front-loading the resource would have helped.

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 and all three optional parameters are documented, so the definition is minimally viable. However, the ambiguity with social_accounts_list and the absence of any pagination or filtering context leave real gaps for an agent choosing among six siblings.

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%: name (contains filter), page (pagination), and channel (enum of six networks) are all documented in the schema. The description contributes no additional meaning, so the baseline of 3 applies.

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?

The description does name a resource (competitors / tracked social accounts) and an explicit retrieval action, but the phrasing 'used to get ... and/or public social media accounts' blurs the boundary with the sibling social_accounts_list, and it never explains how this differs from social_competitor_stats_list or social_competitor_posts_list.

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 tool, when not to, or which sibling to prefer for related queries. With six sibling tools in the same family, that omission leaves the agent to guess.

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