delete_private_link

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

With no annotations provided, the description must convey behavioral traits. 'Delete' implies irreversibility and potential cascade effects, but the description does not elaborate on what happens upon deletion (e.g., whether bookings referencing the link are affected). This partial disclosure is adequate but not thorough.

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 a single, concise sentence that front-loads the action and resource. Every word serves a purpose. Could optionally add more details without bloat, but current length is effective.

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?

Given the tool has only two parameters, 100% schema coverage, and no nested objects, the description is mostly adequate. However, since there is no behavioral context beyond 'Delete' and the enterprise note, completeness is moderate. The output schema exists but is not described, which is acceptable per rules.

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 both link_id and event_type_id are documented with their types and descriptions. The description does not add further semantic detail beyond what the schema provides (e.g., how to obtain link_id or event_type_id). 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 clearly states the action ('Delete'), the resource ('private booking link'), and notes it's enterprise-only with parentheses. It distinguishes from sibling tools like create_private_link, update_private_link, and list_private_links by conveying the destructive 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?

No guidance on when to use this tool versus alternatives (e.g., update_private_link) or when not to use it. The enterprise mention implies constraints but doesn't list prerequisites or required permissions.

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