Repeat Set

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

Annotations already declare readOnly=false, destructive=false, idempotent=false and openWorld=true, so the safety profile is covered structurally. The description adds that result files are saved to disk and their paths returned, which is real behavioral value given there is no output schema, but it omits long-running/async behavior (wait, timeout_seconds) and the credit/billing implications implied by estimate_only and unlimited_bundle.

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 purpose is front-loaded, but the third sentence redundantly re-lists the same five modes already enumerated in sentence two ('block, half brick, half drop, mirror or step'), and 'turn the design into a seamless repeat' is echoed in the 'Best for' clause. The repetition costs it a point.

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 15-parameter tool with no output schema, the description covers the essential missing piece, namely that outputs are written to disk and returned as paths. The remaining parameters (dpi, brushes, review_settings, timeout) are fully explained in the schema, so the description is largely complete, though it says nothing about the billing/credits dimension implied by estimate_only.

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% and each parameter carries its own rich description (including the 'never choose for the user' guidance on mode parameters), so the schema does the heavy lifting. The description only restates the repeat-type enum, which is already fully documented, adding no syntax or format detail 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?

The description names a specific verb+resource ('turn the design into a seamless repeat') and enumerates the concrete repeat modes (block, half_brick, half_drop, mirror, step). No sibling tool performs a repeat/tiling operation, so an agent can cleanly distinguish this from tools like td_vectorizer or td_fabric_texture_removal.

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?

'Best for: turning a design into a seamless repeating tile for fabric, wallpaper or rotary printing' gives clear when-to-use context and the target domains. It does not name an alternative tool or state when NOT to use this one, so it stops short of the 5-level routing guidance.

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