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

Annotations only cover the safety profile (readOnly=false, destructive=false, idempotent=false, openWorld=false). The description adds concrete behavioral facts beyond them: an authentication requirement, a metered cost (1 Suite run, with Intelligence including free runs), and that the result persists as a Design Studio project rather than being returned ephemerally.

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?

Two sentences, no waste: the purpose and output shape come first, followed by the cost/auth prerequisites. Nothing is repeated from annotations and nothing extraneous is included.

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 no output schema, the description does the work of explaining the returned artifact (a stored spec covering format, materials, dimensions, quantity, assumptions). Purpose, auth and cost are all covered; the only real gap is parameter-level detail, which is scored separately.

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%, so the description must carry parameter meaning, but it only loosely maps 'plain-language packaging brief' to the required 'brief' argument and never mentions 'project_name' nor the length ceilings. Two undocumented parameters leave the schema as the sole source of truth.

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?

States a specific verb+resource ('Turn a plain-language packaging brief into a structured spec') and enumerates the resulting content (format, materials, dimensions, quantity, assumptions). No sibling tool performs this transformation, so its scope is unambiguous against the pricing/index/quote tools it sits beside.

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?

Gives clear usage context plus prerequisites absent from siblings: it needs a signed-in OPN account or API key and consumes 1 Suite run. It stops short of naming the close cousin cost_packaging_spec or stating when to prefer this over it, so the routing guidance is implicit rather than explicit.

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