Delete contact list

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

The destructiveHint annotation already communicates the destructive nature, and the description adds the authentication requirement (KUDOSITY_API_SECRET) and v1 auth context. However, it does not disclose other potential behavioral traits such as irreversibility or side effects beyond what the annotation implies.

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, immediately followed by the auth requirement. No waste or 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 simple one-parameter delete operation, the description, combined with the schema and annotations (destructiveHint, readOnlyHint), provides all necessary context: what it does, the required parameter, auth needs, and destructive nature. No output schema is needed, and no missing details are apparent.

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 schema covers the single parameter list_id with a clear description ('Numeric list ID to delete'), and the description reiterates 'by ID'. Since schema coverage is 100%, the description adds no additional semantic meaning beyond confirming the parameter's role.

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 the specific action ('Delete'), the resource ('contact list'), and the required identifier ('by ID'). It clearly distinguishes from sibling tools like 'remove_contact_from_list' and 'delete_webhook' by targeting the contact list resource specifically.

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 the tool is used when a contact list needs to be permanently removed, but it does not explicitly state when to choose this over alternatives or mention any exclusions. It does provide the usage context that KUDOSITY_API_SECRET is required, which is helpful but does not offer full guidance.

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