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

The description adds meaningful behavior beyond the annotations: requests are 'limited and deduplicated,' and artwork 'never blocks deployment or publishes itself.' It does not cover failure modes or asynchronous completion, but given the annotations already establish idempotency and non-destructiveness, this is strong additional context.

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?

Three terse sentences front-load the core action, then add constraint and safety context; every sentence earns its place. There is no redundant restatement of the title or schema.

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 4-required-parameter tool with no output schema, the description explains purpose, limitation, deduplication, and non-blocking behavior, which is enough to invoke correctly. It does not mention the response/result or how to retrieve the queued draft, leaving a small gap an agent may need to infer from sibling tools.

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 descriptions cover context and idempotencyKey thoroughly, while application and purpose are bare in the schema. The description only indirectly maps to parameters via 'app's reviewed purpose' and 'deduplicated,' adding marginal meaning without value constraints, examples, or format details.

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 opens with a specific verb and object, 'Queue one premium icon draft,' and anchors it to 'the app's reviewed purpose.' This makes the operation distinct from sibling save/upload/deploy tools by emphasizing 'draft' and explicitly stating that it never publishes itself.

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 wording implies when it should be used: when a non-blocking, premium icon draft is needed from an app's reviewed purpose. 'Artwork never blocks deployment or publishes itself' hints that this tool is not the final save/upload/deploy step, but no alternative tools are named and no explicit when-not-to-use conditions are stated.

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