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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered and the bar is lower. The description adds that output is a single scored report and that adverse-media screening is part of the run, which is genuine value beyond annotations, but it says nothing about runtime, cost, credit usage, or whether screening covers all platforms.

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 duplicated verbatim and both copies are truncated with ellipses, so the text reads as a broken fragment rather than a front-loaded statement. The core purpose is still recoverable from the first clause, but the repetition and truncation waste the limited space available.

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 no output schema and a single opaque nested input object, the description should explain how to supply the creator list and roughly what the scored report contains. It gestures at report contents but leaves input construction entirely undocumented, which is the main thing an agent needs in order to invoke it correctly.

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 nominally 100%, so the baseline of 3 applies. But the single parameter is an opaque nested 'input' object whose only documentation is a pointer to the Apify URL — the description does not say what form the creator list takes (handles, URLs, platform, count limits), so the agent gets no help populating the nested object.

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 ('Vet a list of creators') and enumerates the dimensions checked: engagement rate, fake-follower risk, niche fit, and brand-safety/adverse-media screening. No sibling in the tool list covers influencer vetting, so differentiation is implicit rather than stated, and the sentence is truncated mid-word ('fake-follower…'), which slightly blunts an otherwise clear purpose.

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 phrase 'before you pay them' implies the decision point at which this tool applies, which is useful context. However, it names no alternatives (e.g. generic social listening or review tools) and gives no exclusions, prerequisites, or input requirements, so the agent must infer when this is the right call versus ai_social_listening or tweet_sentiment_intelligence.

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