generate_ornament

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

With no annotations, this description carries the full load and does disclose real behavior: it opens an inline 3D stage, hosted connections attach a browser stage link, oversized meshes are decimated automatically, and there is a 3/month free-tier cap. Missing pieces are what gets returned (a PNG? a saved design handle?) and what happens on quota exhaustion or failure, so it stops short of a 5.

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 is front-loaded, but the body is bloated and repetitive: the inline 3D stage is described twice (once inline, once in the all-caps INLINE 3D STAGE block), and a pricing URL plus quota marketing copy occupy space that should carry input guidance. Several sentences do not earn their place in a tool 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?

Given no output schema and 13 loosely documented parameters, the description covers the headline behaviors (stage, decimation, quota) but leaves the return value, save/persistence behavior, valid enum values, and failure modes unexplained. Adequate to call the tool, not adequate to call it correctly on the first try.

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?

The description adds nothing about any of the 13 parameters. Schema coverage is nominally 100%, but the entries only say things like 'Default: "circle"' with no valid-value list, so shape and material have no enums and no explanation of what 'front', 'back', 'photo_mask', 'brief_id', or 'color_overrides' actually accept. Baseline 3 applies given the stated coverage, but the gap is real.

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 first sentence gives a specific verb+resource: 'Generate a hanging ornament with optional decoration.' That is enough to tell it apart from mesh, slicing, and decoration tools. However, it never distinguishes this from the many sibling product generators (generate_keychain, generate_coaster, generate_nameplate) whose names it sits beside, so sibling differentiation is only partial.

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 'MAKE DOORS' paragraph explains the tool chain (design_session is unavailable here, compile_scad is the make→preview→iterate loop) and states a quota, which is useful routing context. But it never says when a user should ask for an ornament instead of another generate_* product, nor what preconditions or inputs make a good request. Usage is implied, not prescribed.

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