Swagger: Delete Portal Product

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the description only needs to add context rather than repeat the danger. It adds the useful nuance that deletion is scoped to a specific portal, but it doesn't state whether deletion is permanent or has cascading effects; the annotations cover the basic destructive profile.

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 lead sentence is short, specific, and front-loaded. The subsequent 'Toolset' and 'Parameters' sections are mostly redundant with the schema, but the overall size is still small and not distracting.

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 single-parameter delete operation with a rich annotation set and an output schema, the description is nearly complete. It identifies the operand (portal product), the required identifier format, and the portal-scoped behavior; only irreversible side effects are left implicit.

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 the schema already documents productId fully. The description repeats the same text and adds no new meaning beyond what is structured, so the baseline of 3 is 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?

The description opens with a specific action and resource: 'Delete a product from a specific portal.' This clearly distinguishes it from sibling tools like swagger_create_portal_product or swagger_update_portal_product, and the title reinforces the same meaning.

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 description implies when to use this tool: whenever a product needs to be removed from a particular portal. It does not explicitly name alternatives or exclusions, but the delete verb plus the portal-scoping phrase provides enough context for an agent to choose it over create/update/list siblings.

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