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

Annotations already declare destructiveHint=true, openWorldHint=true, and non-idempotence, so the safety profile is covered. The description's real contribution is defining what is preserved versus removed, which is valuable for a destructive edit. However it says nothing about how far the cleanup goes (people, pets, wall decor?), or that the source image is not retained — relevant for a destructive, non-idempotent operation.

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?

Front-loaded with the trigger condition, followed by the scope constraint — well ordered. The trailing 'This matches the Declutter Room workspace card' is UI-selection metadata rather than invocation guidance, but it is short and harmless.

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?

An output schema and rich annotations mean the description needn't explain returns, and the schema covers the image payloads. What is missing is behavior an agent would want before spending a call on a destructive, non-idempotent edit: output resolution/aspect ratio preservation and whether small decorative items on surfaces are also removed.

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%, so the image input formats (download_url, base64 variants) and the optional additional_instructions are fully documented in the schema itself. The description adds no further meaning about when to supply additional_instructions or how preferences interact with the fixed 'keep furniture' behavior, so baseline 3 applies.

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?

States a specific transformation on a specific resource: remove clutter and visual mess from a room while preserving major furniture and architecture. The scoping clause ('keeping the major furniture and architecture') implicitly distinguishes it from empty_room, but no sibling is named explicitly.

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?

'Use when the user wants clutter and visual mess removed while keeping the major furniture and architecture' is a clear activation condition with a built-in exclusion (heavy edits like emptying the room belong elsewhere). It stops short of naming the alternative tool to use for full removal, which is the only gap.

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