Load a Zé category

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds a strange note about 'live 200 with checkout-information-not-found without session' which does not clarify behavior in a useful way and may confuse the agent about session dependencies. No contradiction, but no added value.

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 cryptic sentence that is short but not effectively concise. It omits essential details and uses opaque jargon, sacrificing clarity for brevity. It reads as under-specified rather than deliberately compact.

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?

With no output schema, no parameter explanations, and no usage context, the description is functionally incomplete. An agent cannot reliably determine expected inputs, return format, or error conditions, making correct invocation highly unlikely.

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 must compensate by explaining category_id, privacy_mode, and response_format. It mentions none of these parameters, leaving the agent without any guidance on required identifiers or how the enum options affect the result.

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 says 'Read-only loadCategory' which essentially restates the tool name without explaining what loading a category entails. The parenthetical 'live 200 with checkout-information-not-found without session' is cryptic and gives no clear functional meaning, nor does it distinguish this from siblings like ze_list_categories.

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 on when to use this tool versus alternatives such as ze_list_categories, ze_product_detail, or ze_checkout_preview. No context about appropriate scenarios, preconditions, or exclusions is provided.

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