image_background_remover

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

With no annotations and a description that repeats the name, there is no disclosure of behavioral traits such as whether the tool modifies files, requires authentication, or has rate limits. The description is entirely uninformative.

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 extremely short but at the expense of providing any useful information. It is a single line of all-caps text that does not earn its place.

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 absence of an output schema and any parameter details, the description should explain what the tool does (e.g., removes background from an image input). It completely fails to provide a complete picture, leaving the agent guessing.

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 and 100% schema coverage, so the schema already fully defines the input. The description adds no additional meaning, but the baseline is 3 due to no missing param info.

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 is 'IMAGE BACKGROUND REMOVER', which merely repeats the tool's name without any verb or clarification of what exactly 'remover' does (e.g., processes an image, returns a URL?). This tautology fails to specify the tool's purpose.

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?

No context is provided on when to use this tool versus alternatives like 'text_to_image_fast_and_high_quality' or 'get_img_url'. The description offers no practical guidance.

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