deleteProfile

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

Without annotations, the description fully discloses the irreversible and destructive nature, stating that settings, lists, and analytics data are permanently removed. It does not mention prerequisites like authentication or immediate effect, but for a simple delete tool, it provides sufficient behavioral context.

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 concise with three front-loaded sentences: a striking warning, the irreversible action, and a safety reminder. No unnecessary words; every sentence adds value.

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 no output schema and one parameter, the description covers all necessary context: action, irreversibility, scope of deletion (entire configuration), and a usage caution. It is fully adequate for an agent to understand and invoke this tool safely.

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 single parameter profile_id has a complete description in the input schema (6-character alphanumeric identifier). The tool description does not add extra meaning or context beyond what is already provided in the schema, so baseline 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 clearly states the tool permanently deletes a NextDNS profile and all its configuration. The verb 'delete' is specific, and the resource is precisely identified. It distinguishes itself from sibling tools like createProfile, getProfile, and updateProfile by emphasizing the irreversible nature.

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 includes a safety warning to only delete profiles you own and are certain, implicitly guiding when to use. However, it does not explicitly contrast with alternatives like updateProfile for non-destructive changes. The guidance is clear but lacks explicit when-not-to-use details.

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