Estimate Website Traffic Rank

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

The annotations already mark the call read-only and idempotent, but the description adds substantial non-obvious behavior: it requires an APIFY_TOKEN and consumes Apify credits per call, lower rank numbers are better, trends are expressed in words, and not_found is a normal outcome for most B2B domains. This goes well beyond what the annotations alone provide.

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 dense and front-loaded: it leads with the main output, then covers the critical rank-versus-traffic distinction before moving to caveats and requirements. It has a slight redundancy around 'ranks, not traffic,' but every sentence otherwise contributes non-obvious operational context.

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 eight parameters and no output schema, the description covers the essential return semantics (rank, date, band, trend, one flat Clay-ready row) and the main operational caveats (authentication, credits, skipped-vs-not_found source behavior, B2B coverage gaps). An agent has enough context to select the tool and interpret its result 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 100% with detailed per-parameter descriptions, so the baseline is 3. The description adds interpretive value beyond the schema, such as setting expectations that most B2B domains will return not_found and clarifying that the result is a rank rather than traffic data. It does not enumerate parameters, but the schema already covers that thoroughly.

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 opens with a specific verb and precise resource: it returns a research-grade popularity rank for a company domain from the public Tranco list. It further distinguishes itself by naming the output pieces (rank, date, band, trend) and explicitly stating it will never return a visit count.

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 description gives strong usage expectations, including when a result is meaningful and when it is not: 'Most B2B domains are not on the list at all and return not_found, which is normal rather than disqualifying.' It also warns that ranks do not convert to visits, so this tool cannot be used as a traffic-count source. With no sibling tools, explicit alternative routing is unnecessary.

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