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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description's 'Permanently' adds emphasis rather than new information. The confirm-gate mention is useful context beyond the boolean flag, but it largely restates the schema. No detail on irreversibility consequences, cascade effects, or error behavior.

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 zero filler; the destructive nature and the confirmation requirement are both front-loaded. Nothing could be removed without losing signal.

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 two-parameter destructive tool with annotations declaring its safety profile and no output schema, the description covers the essentials: what is deleted, where, and the confirmation gate. Slightly short on consequences for an irreversible operation, but nothing an agent strictly needs is missing.

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%, and both parameters are documented in the schema itself, so the schema carries the semantic load. The description's mention of confirm:true duplicates the schema text rather than adding format or edge-case meaning. 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 and resource ('permanently delete a product') scoped to 'its Meta catalog', which distinguishes it from update_catalog_product and list_catalog_products without naming them. Clear enough that an agent knows exactly what operation is performed.

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 prerequisite ('Requires confirm:true') is stated, implying the tool will not act without explicit confirmation. However, there is no guidance on when to choose deletion versus update_catalog_product, nor any warning about checking the product exists or is referred to by other objects.

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