markitup_remove_background

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

Discloses output is transparent PNG, cost of 1 credit, free for Pro/Power subscribers. No annotations provided, so description carries burden; it covers key behaviors but omits error handling or rate limits.

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?

Two sentences, front-loaded with purpose, then cost and input format. No wasted words.

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 medium-complexity tool, description covers purpose, input, output, and cost. No output schema, but output described as transparent PNG. Enough for agent to decide.

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 has 67% description coverage. Description adds context that image_url and image_base64 are mutually exclusive and mentions mime_type default. Adds some value, but schema already covers basics.

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 it removes background from an image using Photoroom HD AI, returns transparent PNG. Distinct from siblings (credit_balance, extend, generate, regen) which are unrelated.

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?

Specifies input format (URL or base64) and credit cost. Implicitly suggests usage for background removal, but no explicit when-to-use or alternatives among siblings.

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