estimate_decoration_cost

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

With no annotations at all, the description carries the full behavioral burden. It does disclose one genuinely useful fact — that the tool requires a Pro subscription — but says nothing about whether it reads files from disk, whether it is read-only, what the cost model includes, or what the result looks like (and there is no output schema to fall back on).

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 purpose sentence is correctly front-loaded, but the majority of the text is a Pro-tier marketing pitch and a tracking-parameterized upgrade URL. None of that helps an agent decide or invoke the tool; it is wasted tokens in the definition.

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?

Eight parameters, two of them required file paths with unexplained semantics, no annotations, and no output schema. The description does not explain what the returned cost represents (total vs delta), what materials/labor assumptions apply, or how the required paths relate to each other.

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 coverage is 75% and the schema 'descriptions' are only default values ('Default: "PLA".', 'Default: 0.0.'), which carry almost no semantics. The prose adds nothing about the non-obvious required pair base_model_path/decorated_model_path — the crux of the delta calculation — so the description fails to compensate for the gap.

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 line gives a specific verb and resource ('Estimate cost impact of decorating a model') and the '(Pro)' marker signals a gated capability. However, it never distinguishes this from the many cost-estimation siblings (estimate_cost, estimate_material_cost, estimate_print_cost_from_mesh, estimate_batch_cost), so an agent cannot tell why it would pick this one.

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 only actionable guidance is the prerequisite 'Requires Kiln Pro', which is useful but is a gate, not a usage rule. There is no statement of when to use this versus the other cost tools, no mention of what the two required model paths must represent, and no exclusions.

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