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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is covered and the description's mention of 'delete' is consistent. The description adds member-management context beyond the annotations, but does not disclose that deletes are irreversible, whether deleting a parent affects children, or how idempotency_key deduplicates retries.

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?

A single front-loaded sentence with no filler that covers the tool's scope efficiently. It is compact, though the brevity contributes to the missing usage and parameter detail elsewhere.

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?

This is a 10-parameter, destructive, enum-driven mutation tool with no output schema and zero schema descriptions; the one-line description is far too thin to let an agent map actions to required fields or understand failure modes. It should explain the action/kind pairing and idempotency requirement.

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% across 10 parameters, so the description carries the full burden and largely fails: it implies title (rename) and members, but never explains kind, action values, ref, handle, active, parent, workspace, or the required idempotency_key. Six of ten parameters remain semantically opaque.

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 specific verbs (create, rename, delete, change members) and specific resources (collections, categories, customer groups), so an agent can distinguish it from catalog_list and catalog_import. However, it says 'rename' while the action enum also supports generic 'update' of fields like active/handle/parent, so the stated purpose is narrower than the actual capability.

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?

No guidance on when to use this versus catalog_import (bulk import) or catalog_list, and no prerequisites (workspace scoping, idempotency key requirement) are mentioned. The agent must infer usage entirely from the name and schema.

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