Delete CDP Guest Profile

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

Beyond the annotations, the description adds meaningful behavioral context: the operation is irreversible, permanently deletes associated data, and is unverified against Sitecore's official docs. It also warns the agent to confirm behavior with curl/Postman before relying on it, which is valuable operational transparency.

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 description is compact and well-structured: the core action is front-loaded, followed by the destructive consequence and a practical verification warning. Every sentence adds meaningful information without redundancy.

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 destructive operation, the description covers the action, consequences, typical use case, and reliability caveat. No output schema exists, but none is needed for this type of operation, and the guidance is sufficient for correct invocation.

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?

The input schema already fully documents the only parameter, guestRef, with a clear description. Since schema coverage is 100%, the tool description does not need to add parameter-level details, and the 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?

The description states a specific verb ('Permanently deletes') and a specific resource ('guest profile and its associated data from Sitecore CDP'). It clearly distinguishes this tool from the read/search/upsert sibling tools by emphasizing the destructive nature of the operation.

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 clear usage context by noting it is 'typically used for privacy/right-to-be-forgotten requests' and warns that the endpoint is unverified. It does not explicitly name alternatives or when-not-to-use conditions, but no close non-destructive alternative exists among siblings.

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