add_registry_item

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

Annotations only provide destructiveHint: false, which is minimal. The description adds the default-collection lookup behavior, but this largely repeats the collection_id parameter schema. It does not disclose whether adding an already-present SKU is idempotent, what happens if the SKU is invalid, or what the tool returns after a successful add.

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?

The description is a single, tightly worded sentence with no filler. The core action is front-loaded, and the only conditional detail — default collection lookup — is relevant and expressed efficiently.

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 straightforward add operation with a fully documented schema, the description is reasonably complete. It states the action, the identifier type, and the key default behavior. It does not discuss errors or return values, but the absence of an output schema and the simplicity of the operation make this only a minor gap.

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 the schema fully documents all five parameters. The description adds little parameter meaning beyond the schema; it just confirms the SKU is used to identify the product and that collection_id defaults. Baseline 3 is appropriate.

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: "Add a product (by SKU) to the registry." This clearly differentiates it from sibling tools like update_registry_item, remove_registry_item, and search_registry_products, all of which act on registry items but are distinct actions.

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?

The description gives no explicit guidance on when to choose this tool over alternatives like update_registry_item or remove_registry_item. It implies usage by its action verb, but does not state prerequisites, exclusions, or conditions under which a sibling tool would be more appropriate.

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