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

Annotations already mark this as destructive (destructiveHint=true), and the description reinforces this by saying 'Remove' and 'Confirm with the user first.' It adds useful behavioral context about sourcing the parameters from swop_get_my_smartsite, which is beyond what the annotations convey.

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 focused sentences deliver the core action, the item categories, the parameter sourcing workflow, and the user-confirmation requirement. There is no filler or repetition of already-available schema 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?

For a destructive removal tool with strong annotations and full schema coverage, the description provides everything an agent needs: what to remove, how to identify the target, the exact source of identifiers, and the required user confirmation. No output schema is needed for a removal action.

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?

Although schema coverage is 100%, the description adds meaning by explaining the relationship between itemId and contentType and how to obtain them from swop_get_my_smartsite. The mapping from contentType enum values to real-world item categories provides semantic value beyond raw enum names.

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 uses a precise verb ('Remove') and clearly defines the resource: links/icons/info-bars/product tiles from the SmartSite. It distinguishes itself from siblings like swop_add_link by focusing on the removal use case and enumerating the exact item categories.

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 gives explicit how-to guidance: obtain the item's id and contentType from swop_get_my_smartsite, including a mapping from human-friendly categories to contentType enum values. It also instructs the agent to confirm with the user first, which is critical for a destructive operation.

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