inpaint

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

With no annotations provided, the description carries full burden and adds valuable behavioral context: it discloses the monetary cost ($0.15) and access requirements (Tier 1+), which are crucial for usage decisions. However, it doesn't mention rate limits, response format, or error conditions.

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 concise with just two sentences that each earn their place: the first explains the core functionality, and the second provides critical operational constraints (cost and requirements). No wasted words or redundant information.

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 mutation tool with no annotations and no output schema, the description covers the basic purpose and constraints well but lacks information about what the tool returns (e.g., edited image URL, status) and potential side effects. Given the complexity of image editing, more output information would be helpful.

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 description coverage is 100%, so the schema already documents all three parameters thoroughly. The description doesn't add any parameter-specific information beyond what's in the schema, maintaining the baseline score of 3 for high schema coverage.

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 purpose with specific verbs ('remove or replace objects') and identifies the resource ('image') and method ('AI inpainting'). It distinguishes from siblings like 'background_remove' (specific background removal) and 'ai_edit' (broader editing) by focusing on object-level inpainting.

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 implies usage for object removal/replacement in images, but doesn't explicitly state when to use this versus alternatives like 'background_remove' (for backgrounds only) or 'ai_edit' (for general edits). It mentions cost and tier requirements, which provide some context but not comparative guidance.

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