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

Annotations already flag destructive/idempotent, but the description adds substantial context: the unpublish cascade (public page, QR, embeds go quiet), removal of item memberships while leaving items intact, clearing of the primary-catalog pointer, permanence, and the demo-catalog 409. This is exactly the extra behavioral detail the structured fields do not carry.

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?

Front-loaded with the core action and its key side effect, then the cascading consequences. Slightly dense semicolon-chained prose, but nearly every clause conveys distinct, non-redundant information.

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?

No output schema exists, yet the description covers auth scope, failure mode (409), permanence, and downstream effects on memberships, public page, and primary-catalog pointer. An agent has everything needed to invoke it and anticipate the result.

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 coverage is 100%, so both id and idempotency_key are already documented in the schema, including the retry semantics of the idempotency key. The description adds no parameter-specific syntax or format detail, so baseline 3 applies.

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 (delete) and resource (catalog), and the parenthetical clarifies the side effect up front. Sibling list is dominated by item-level tools, and the description makes clear this operates on a catalog rather than an item.

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?

Explicitly states one cannot delete the platform demo catalog (409 conflict) and that the scope write_catalog is required, which are real preconditions. It does not name a sibling alternative or describe when to prefer this over, say, unpublishItem, but the conditions given are concrete.

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