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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds nothing beyond repeating the title — no word on input requirements, whether it hits live LLMs (cost/latency), auth needs, or how many prompts/platforms are queried, which matters for an open-world scraping-style tool.

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 text is duplicated and truncated ('…' then an overlapping restatement), so roughly half the description is wasted. The useful content is buried rather than front-loaded.

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?

With no output schema and an opaque nested input object, the description should explain what goes in and what comes back. Instead it only names the platforms, leaving an agent unable to construct a correct call or anticipate the result shape.

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?

Only one parameter exists (a nested 'input' object) and the schema claims 100% coverage, so baseline is 3. But the parameter's description is a generic pointer to the Apify URL and no nested fields are surfaced, so the description does not clarify what must actually be supplied (brand, competitors, prompts, platforms).

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 clear verb+resource (measure brand share of voice) and the covered platforms plus the outputs (competitor comparison, citation mining). However, it does nothing to distinguish this tool from close siblings such as ai_brand_visibility, ai_brand_accuracy, ai_citation_miner, or ai_search_visibility_platform, leaving the agent to guess which overlapping tool to pick.

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 explicit when-to-use, when-not-to-use, or alternative routing guidance. The only usage signal is the implied 'if you want share of voice, use this,' which is insufficient given the crowded set of near-duplicate AI-brand siblings.

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