get_product_faces

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

With no annotations, the description carries full behavioral burden; it does disclose a real access constraint ('Requires Kiln Pro'), which is useful. However, the claim that this tool includes 'calibration that learns your printer, mid-print edits, and unlimited textures and decorations' misrepresents the behavior of a face-registry lookup and would confuse an agent about side effects or scope.

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?

Only the first sentence serves the tool; the following three are marketing copy and an upgrade URL that consume roughly three quarters of the text. Concise intent is buried under sales material.

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?

A one-parameter, no-output-schema tool needs the valid product types and a sense of what a 'semantic face registry' returns; neither is given. The space that should carry that information is spent on tier promotion instead.

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 0% for the single required parameter, so the description must compensate, and it does not: it never says what values 'product_type' accepts or that list_product_types supplies them. Only the bare phrase 'for a product type' is added.

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 opening sentence gives a specific verb and resource ('Return the full semantic face registry for a product type'), but it never distinguishes this from close siblings such as list_decoratable_faces, get_product_color_roles, or describe_face. The remaining three sentences describe plan features rather than the tool, muddying what it actually does.

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?

There is no guidance on when to use this instead of list_decoratable_faces, describe_face, or list_product_types, which appear to cover overlapping ground. The only conditional statement is a pricing/upgrade one, not a usage rule.

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