dns_delete_primary_server

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

Description does not disclose behavioral traits beyond the obvious delete action. No annotations are provided, and the description doesn't mention side effects, irreversibility, dependencies (e.g., whether records must be deleted first), or permissions needed.

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, short sentence, which is concise but under-specified. It lacks structure and fails to front-load key details like the required parameter or behavioral notes.

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?

The description is incomplete for a delete operation. It doesn't mention what the tool returns (though output schema exists but isn't described), or any post-deletion effects. Given the parameter simplicity, more context is needed.

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 coverage is 0% for the only parameter 'primary_server_id', and the description adds no meaning. The agent is left to infer that this is the identifier of the primary server to delete, but no format, source, or constraints are given.

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 it deletes a primary server. It is concise and unambiguous, though it lacks context about what a primary server is. It distinguishes from sibling tools by being specific to DNS primary server deletion.

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 usage guidelines provided. There is no information on when to use this tool versus alternatives (e.g., dns_delete_zone or dns_delete_record), nor any prerequisites or conditions for safe usage.

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