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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The one piece of added context is content scope: the response carries the design and preview images, which is useful for an agent deciding whether it needs a follow-up call. Nothing about auth, rate limits, or missing-look behavior.

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?

A single short clause with zero padding, and the most useful information (what comes back) is placed immediately. It is under-specified rather than bloated, and the missing verb makes it slightly cryptic.

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 one-parameter read tool with no output schema, the description does the minimum necessary by telling the agent what the payload contains. An agent would still not know how a nonexistent look_id is signalled, but annotations and the single-parameter schema leave little else to guess.

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?

There is one parameter with 100% schema description coverage, so the schema documents look_id fully. The description adds no format, source, or lookup guidance beyond it, which is the expected baseline when the schema does the heavy lifting.

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 fragment names a specific resource ('One Look') and discloses the payload ('its design and preview images'), which is enough to separate it from list_looks and the rename/delete/visibility siblings. It lacks an explicit verb, so it reads as a caption rather than a task statement.

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?

Nothing states when to call this rather than list_looks or get_artist, nor any precondition on look_id. The singular-vs-plural contrast with list_looks is inferable at best.

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