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

Annotations already declare it as a read-only, idempotent, closed-world, non-destructive call, so the safety profile is covered. The description adds value beyond that by enumerating what the response contains (pictures, design_id, unfinished items, shop-check gaps) and the omitted-argument default, which annotations cannot express.

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?

Two sentences, front-loaded with the resource and its contents, followed by the default behavior. Every clause carries information; the phrasing 'anything the shop's own check found missing' is slightly roundabout but not wasteful.

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?

No output schema exists, so the description must carry the return-value burden, and it does so by listing the main response components. Formatting and ordering details are unspecified, but an agent has enough to interpret the result and call the tool correctly.

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?

With a single parameter at 100% schema coverage, the schema already documents drawing_id and its pattern. The description goes further by defining the semantics of omitting it (falls back to the conversation's newest drawing), which is behavior the schema cannot convey.

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?

Names the resource (a drawing) and states what it reports: pictures so far with design_id, in-progress work, and shop-check findings. That is specific enough to separate it from draw_from_photo, draw_shirt, and show_shirt, though the verb is implied rather than stated.

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?

Provides one real usage rule — omit drawing_id to read this conversation's newest drawing — which is useful context. However, it never says when to prefer this tool over siblings like show_shirt or the drawing tools; usage is only implied by the status-oriented content.

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