Get my ScrapingBot credits

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

It goes beyond standard metadata by disclosing crucial operational details like 'Costs no credit,' the specific failure code (HTTP 402), and the link to upgrade plans, adding significant behavioral context.

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?

While slightly verbose, every part of the paragraph is high-value operational instruction. The critical information (what it does and when to use it) is front-loaded effectively.

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?

Given the lack of an output schema, the description provides a complete narrative of the account data, including renewal cycles and failure modes, leaving no critical data gaps.

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?

Since there are zero parameters, the baseline score is 4. The description effectively explains the scope of the data return, which is the only thing an agent needs to know about the 'input' operation.

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 clearly specifies the data retrieved (plan, used, remaining, reset time, and upgrade page) for the ScrapingBot account, distinguishing it from general data scraping siblings.

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?

It provides explicit guidance on when to use the tool—'Check it before a series of scrapes'—and provides a clear operational trigger for invocation: low credit alerts or HTTP 402 failure.

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