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

The annotations only declare the generic safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), while the description adds substantive lifecycle behavior: the collection is hidden, is discarded with the draft, and only becomes live on publish. That is exactly the kind of context annotations cannot convey. It omits any note about duplicate creation (relevant given idempotentHint=false) or auth/permission requirements, keeping it from 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?

Three short sentences, front-loaded with the core action, then the lifecycle consequence, then the usage restriction. No filler or redundancy; every sentence contributes a distinct fact.

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?

For a nested-object mutation with no output schema, the description covers the object's visibility and persistence semantics well but says nothing about the result (e.g. whether a collection id/ref is returned for later use) or how the required draft ref is obtained. Adequate to call correctly, incomplete for understanding the outcome.

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 67% with a nested collection object, and the description adds no parameter meaning at all — it never mentions the draft ref, store selection, or collection fields. The schema largely carries this burden, so the baseline 3 is appropriate, but the undocumented remainder (store, templateSuffix, sortOrder, relation) is left to the schema alone.

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 states a specific verb and resource ('Create a new hidden collection in a Fudge draft') and names the parent container, which distinguishes it from siblings like create_draft_product or create_draft_page by resource alone. It stops short of explicitly naming or contrasting any sibling tool, so it lands at a clear-but-undifferentiated 4.

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?

'Use only when the merchant asks' gives a real when-not condition (do not create proactively), which is more than most mutation tools offer. However, it offers no guidance on when this is the right call versus creating products/pages in the draft, nor any prerequisite or sequencing advice, leaving usage only partially implied.

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