add_registry_item

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

Annotations already declare openWorldHint=true and destructiveHint=false, so the safety profile is covered and the description adds the default-collection auto-lookup behavior. It does not disclose duplicate handling, idempotency, or validation/failure behavior for an invalid SKU — meaningful gaps for a mutation tool.

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 filler, with the core purpose front-loaded and the fallback behavior immediately after. Nothing could be removed without losing information.

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 low-complexity mutation tool with full schema coverage and no output schema, the description covers purpose and the one non-obvious default behavior. Remaining gaps — duplicate SKU handling and error behavior — are minor given how thin the tool's surface is.

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 100%, so all five parameters are already documented in the schema, including defaults for quantity, most_wanted, and enable_group_gifting. The description only restates the collection_id default rule, adding no syntax or format detail beyond the schema, so the baseline of 3 applies.

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 and resource ('Add a product (by SKU) to the registry'), which clearly separates it from sibling tools like update_registry_item and remove_registry_item. It does not name siblings explicitly, but the add/update/remove distinction is self-evident from the verb.

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?

Provides one useful conditional rule ('If collection_id is omitted, the default collection is looked up automatically'), which is usage-relevant. However, it gives no guidance on when to use this versus update_registry_item, or what happens when the SKU already exists in the registry.

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