Outscraper Balance

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

No annotations are provided, so the description carries the full burden. The verb 'Fetch' implies a read-only operation, and the content emphasizes account status and billing details. However, it does not explicitly state that the tool has no side effects, does not consume credits, or require special permissions beyond the active API key, which would strengthen transparency.

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 well-structured with a lead sentence followed by bullet-point sections. It is slightly repetitive between 'Best for' and 'Use this when', but each bullet carries meaningful information and the main point is 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?

Given the tool's simplicity (zero parameters) and the presence of an output schema, the description adequately covers purpose, usage context, and decision-making scenarios. It answers why and when to use the tool without needing to describe return values, which are handled by the output schema.

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?

The tool has zero parameters (input schema properties are empty), so per the baseline rule for 0 params, the description need not explain parameter semantics. The mention of 'active API key' adds useful context about implicit authentication.

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 states the tool's function: 'Fetch the current Outscraper account balance and billing summary for the active API key.' This uses a specific verb (fetch) and names the resource (balance/billing summary), effectively distinguishing it from sibling search and data tools.

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 provides concrete 'Best for' and 'Use this when' sections with explicit scenarios like checking whether the key is attached to a funded account and confirming account status before running larger jobs. It does not explicitly mention alternatives or when-not-to-use, but the guidance is clear and actionable.

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