Zé product detail

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

The annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint:false. The description only repeats 'Read-only' and adds no new behavioral context such as how privacy_mode affects output or how response_format changes the result. There is no contradiction.

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 very short and front-loaded, stating the operation before the read-only note. It has little fluff, though 'with category' is unclear and somewhat reduces the value of the brevity.

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?

There is no output schema, so the description should indicate what the tool returns, but it does not. With three parameters including two enum-driven modes, the definition is too sparse for an agent to invoke the tool correctly in all cases.

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 0%, so the description needs to compensate for missing parameter docs. It maps product_id to 'id' but leaves privacy_mode and response_format unexplained, despite both having meaningful enum options. The schema provides the enum names, but not their semantics.

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 names a concrete operation and resource ('loadProduct(id)') and marks it read-only, so an agent can tell this fetches product details. However, the phrase 'with category' is ambiguous and no sibling tool is named, so it does not explicitly distinguish itself from tools like ze_search or ze_load_category.

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 guidance about when to use this tool instead of alternatives such as ze_search, ze_load_category, or ze_checkout_preview. 'Read-only' is a safety property, not a usage condition, so the description does not help an agent decide when to call this function.

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