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

Annotations only declare readOnlyHint=false and openWorldHint=true. The description omits key behavior for an image generation job: whether the call is synchronous or returns a task handle to poll (a nexscope_media_task_result sibling exists), cost/latency, and that masks must be pixel-aligned with their sources. No contradiction, but little added value.

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?

One front-loaded sentence with no filler; the core action comes first and the optional-mask capability follows. It is arguably too terse rather than too long.

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?

A generative mutation tool with no output schema and no async/polling disclosure leaves the agent unsure what comes back and whether to wait or poll. The description does not compensate for the missing return-value information.

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 all five parameters are already documented with examples, including size and 20 MB limits. The description restates that garment and model masks are optional but adds no constraints or interaction rules beyond the schema.

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?

Specific verb+resource: 'Dress a model image with a one-piece outfit or suit image.' The 'one-piece' qualifier implicitly separates it from the tops/bottoms clothes-changer sibling, though 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?

No statement of when to use this versus nexscope_virtual_try_on, nexscope_ai_clothes_changer_for_tops_bottoms, or nexscope_ai_model_swap. The only routing signal is the word 'one-piece', which the agent must infer as an exclusion.

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