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

Annotations only declare non-read-only, non-destructive, non-idempotent. The description adds real behavioral detail beyond that: per-item isolation ('one failure never stops the rest'), the results[i] shape with productId or failure reason, and partial-success marking when extras fail. It also discloses the members-only authorization requirement.

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?

Front-loaded with the core capability and limit, then failure semantics, then auth, then docs link. Four tight sentences with no filler; the field enumeration is the only mildly redundant part.

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 2-parameter but deeply nested mutation with no output schema, the description covers return shape (results[i]), partial-failure semantics, the item cap, and auth. Minor gaps remain: no mention of whether the whole batch is rejected on malformed input versus per-item, and no rate/throughput expectations.

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 50%, but the nested item schema is unusually self-documenting, with every property described inline. The description only re-lists field names (name, description, price, stock, pictures, categories, options, variants) without adding format or constraint meaning, so it neither compensates nor detracts.

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 and hard scope: 'Create up to 30 products in one rikma in one call'. It also anchors itself to the sibling single-item tool ('same fields as createRikmaProduct'), so an agent can distinguish batch from single creation without opening a schema.

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?

Clear context for use (bulk creation, up to 30 items, membership required) and an implicit routing rule via the createRikmaProduct reference. It does not explicitly say when to prefer the single-item tool or what to do if more than 30 items are needed, so no full when-not guidance.

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