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 description is not required to restate it. The description adds a modest amount of behavioral context by implying the output is a set of citing sites per category, but it says nothing about input requirements, coverage limits, engine-specific behaviour, or runtime characteristics despite openWorldHint signalling live external queries.

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 literally a duplicated, truncated sentence ('...cite for…. Find which sites ... cite for your category...'). This is wasteful and structurally broken rather than concise, and the most useful clause (the category framing and the visibility payoff) is buried in the second copy.

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 a nested, effectively undocumented input object and no output schema, the description does not explain what a valid input looks like, what a run returns, or how results are scoped. With openWorldHint set, an agent would reasonably want to know about cost, latency, or query constraints, and none of that is present.

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?

There is a single nested 'input' object whose schema description is only a link to the Apify page, so schema coverage is nominally 100% but carries almost no semantic content. The description's phrase 'for your category' is the only hint about what the input should contain, which is a marginal gain over the schema.

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 names a concrete verb ('Find') and resource ('which sites ChatGPT, Perplexity, Gemini & Google AI Overviews cite for your category'), so an agent knows this is a citation-source discovery tool. It does not explicitly differentiate itself from near-neighbours such as ai_brand_visibility, ai_share_of_voice, or ai_search_visibility_platform, and the text is visibly mangled (truncated with '….' then repeated), which slightly undercuts clarity.

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 trailing clause 'so you know where to get mentioned to win AI visibility' implies the GEO/PR use case, which is enough to place the tool in a workflow. However there is no explicit when-to-use statement, no when-not-to-use, and no named alternative among the many AI-visibility siblings, so routing is left to inference.

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