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

With all annotations false, no safety or behavioral hints are provided, so the description carries the burden. It clearly discloses that the tool queues work asynchronously and returns a job ID, requiring polling. It also mentions Uwear's prompt system and the save semantics. It does not fully detail all side effects, but the key async behavior is transparent.

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 three sentences with no wasted words. It front-loads the primary action, then explains the save distinction, and ends with the required follow-up polling call. Each sentence earns its place and the structure is easy to scan.

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 an asynchronous tool with no output schema, the description covers the essential flow: queue, save vs draft, and polling. It does not mention all parameters, but the schema fully documents them. It also lacks an explicit distinction from the sibling create_art_direction, but the async and job-ID details provide sufficient context.

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?

The input schema has 100% coverage with detailed descriptions for all parameters. The tool description adds value by reinforcing the save parameter's meaning, but it does not provide additional semantics beyond the schema for sources, user_text, image_urls, or reference_image_attachments. The baseline of 3 is appropriate when the schema already documents parameters thoroughly.

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 states a specific action ('Queue the conversation') on a specific resource ('for asynchronous ArtDirection authoring using Uwear's prompt system'). It distinguishes itself from synchronous creation by explicitly mentioning asynchronous processing and returning a job ID. The save=true/false distinction further clarifies the two modes of operation.

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 gives explicit guidance on when to use save=true versus save=false, and instructs the caller to poll get_art_direction_authoring_job until done. It does not explicitly name alternative tools (e.g., create_art_direction or iterate_art_direction), but the async and polling context implies when this tool is appropriate.

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