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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true; the description adds concrete meaning to the non-idempotency by explaining the duplicate-name failure mode, and names the underlying endpoint PUT /v1/categories. It stops short of stating auth requirements or the failure/return shape, so not a 5.

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 short sentences with the operation type front-loaded, then the risk caveat, then the endpoint. Every clause carries information an agent needs; nothing is redundant.

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 three-parameter mutation with full annotation coverage and no output schema, the description covers intent, optional behavior, and the key failure mode. It leaves out what the call returns (e.g. the new category id) and any permission prerequisites, which are minor residual gaps.

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 three parameters (name, slug, products) are already documented in the schema. The description echoes the optional products assignment but adds no format or constraint detail beyond what the schema provides, making the baseline 3 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?

States a specific verb and resource ('create a product category') plus the optional scope of assigning existing products, and prefixes it with 'WRITE:' so the mutation intent is unmistakable. An agent can distinguish it from shoprocket_update_category or shoprocket_list_categories from the description alone.

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 duplicate-call caveat ('calling twice with the same name may create a duplicate or be refused') is genuinely useful operational guidance. However, it never says when to prefer this over shoprocket_update_category, nor what prerequisites (e.g. store context, auth) must hold, so usage is only implied.

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