Estimate Credits

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

With no annotations, the description fully discloses credit cost per mode, resolution limits for input and output, and the workflow (check balance, get confirmation). It transparently defines behavior for both modes and addresses canAfford=false scenario.

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?

All sentences are informative and front-loaded. The description is well-structured with mode blocks and required steps. Slightly verbose but no redundancy; earns its length.

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?

Without output schema, the description covers return values (credit cost, canAfford) and user interaction. It provides all necessary context for a pre-processing estimation tool, including fallback for insufficient credits.

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%, baseline 3. The description adds significant context beyond schema, especially for hdMode (detailed usage conditions) and imageCount (range constraints already in schema but reiterated). It clarifies parameter semantics beyond bare types.

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 estimates credit cost and checks balance, with specific credit rates for fast and HD modes. It explicitly positions itself as a mandatory prerequisite for remove_background and batch_remove_background, distinguishing its role from sibling 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 explicit 'REQUIRED' usage instruction to call before processing tools, including post-call actions (display result, ask user confirmation). It also specifies conditions for HD mode and handling insufficient credits.

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