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

Annotations declare a non-destructive, idempotent write, and the description meaningfully adds to that: choosing the same star retains the existing pack, no image generation occurs, and no credit is charged. Those are exactly the behavioral facts an agent needs before invoking a mutation, and they go beyond what the structured fields say.

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 action and its core constraints are front-loaded in the first two sentences, followed by outcome, idempotency, and cost. Every sentence carries information, though the trailing sentence about generation readiness reads as an appended aside rather than a tightly integrated 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?

With an output schema present, the description needn't document return structure, and it still summarizes the return (saved reference pack plus newly-created flag). Permissions, cost, idempotency, and parameter provenance are all covered, leaving only minor gaps such as failure or error conditions.

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%, so both artistId and starId are already documented in the schema, including the "not an image URL" caveat and the source tools. The description reinforces the starId provenance but adds no format or constraint detail beyond the schema, so the baseline 3 applies.

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 ("saves"), a specific resource (a Brix36 ready-made fictional portrait), and a specific target (an existing artist). It also distinguishes itself from the sibling lookup by noting the starId must come from the ready-made star list, so an agent can tell it apart from studio_ready_made_stars_list without opening either schema.

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?

It states the prerequisites clearly: artist permission is required and starId must be current and sourced from the ready-made star list. It also points to the artist list for generation readiness, giving a clear context of use. It stops short of explicit when-not-to-use or a named alternative tool, which keeps it from a 5.

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