Create store item

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, so the safety profile is covered. The description adds only that items are redeemable with loyalty points; it says nothing about whether creation consumes points, channel defaults (SE_CHANNEL_ID / token channel), duplicate handling, or that non-idempotent creation may duplicate items on retry.

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?

A single tight, front-loaded sentence with zero filler — verb and resource come first. It is efficient, though arguably too sparse rather than too verbose for a 15-parameter creation tool.

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 15-parameter mutation with nested objects and no output schema, the description is thin: it never explains how 'type' drives accessCodes, how quantity.total/-1 means unlimited, or the channel defaulting rule. The rich 93%-covered schema and annotations keep it barely adequate, but a more complex tool would need more prose.

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 93%, so the schema already explains all 15 parameters including nested bot/cooldown/quantity/accessCodes objects. The description adds no parameter-level detail beyond implying a loyalty-point cost. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

"Add an item that viewers can redeem with loyalty points" gives a clear verb (add/create) and resource (a redeemable loyalty-store item), so an agent knows exactly what this does. It does not, however, distinguish itself from the sibling store_items_update/delete/list/get tools — only the name carries that differentiation.

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 when-to-use guidance, no mention of prerequisites (e.g. loyalty must be enabled, a channel must be targeted), and no reference to the sibling update/delete tools an agent would otherwise confuse this with. The reader must infer all triggering conditions.

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