acedatacloud_get_platform_distribution_rank

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

The description discloses the privacy-masking behavior, which is a useful behavioral trait. However, with no annotations provided, it does not mention pagination, ordering behavior, authentication needs, or whether results are limited to certain time ranges.

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?

The description is a single, front-loaded sentence with no filler or redundant information. Every word contributes meaning.

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, so return values are covered. However, the description omits usage context, pagination behavior, and the relationship to sibling rank tools. For a 6-parameter list tool, this is minimally adequate but not complete.

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 67%, with search, time bounds, and ordering already described. The description adds 'privacy-masked' context relevant to search, but limit and offset remain undocumented in both schema and description; they are self-explanatory enough to keep this adequate.

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 uses a specific verb ('Get') and a specific resource ('privacy-masked platform affiliate leaderboard'), clearly conveying what the tool does. It also distinguishes itself from the sibling get_distribution_rank by emphasizing the platform-level scope.

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 guidance on when to use this tool versus alternatives such as get_distribution_rank or list_distributions. No use-case conditions, exclusions, or alternative tool references are provided.

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