hostodo_delete_dns_record

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

The description honestly discloses that the tool is a stub that returns a coming_soon response and does not perform the action. It also warns about secrets. However, without annotations or an output schema, the response structure remains unspecified, which is acceptable for a stub.

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 extremely concise, using two sentences to convey the tool's purpose, current status, and a security warning. No redundant information is present.

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 that this is a placeholder stub, the description adequately explains the behavioral limitation and security concern. However, it could be more complete by briefly describing what the coming_soon response contains or suggesting alternative tools for actual deletion once implemented.

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 100%, with each parameter having a basic description. The description does not add extra context or examples for parameters, but the schema already provides adequate information. The 'Do not send secrets' note is a usage guideline, not parameter-specific.

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 a DNS record) and resource (DNS record). It immediately identifies the tool as a stub, which is distinct from sibling tools like hostodo_create_dns_record and hostodo_update_dns_record. However, the 'Coming soon' prefix may cause temporary confusion about intended function.

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 warning about not sending secrets but provides no guidance on when to use this tool versus alternatives, such as whether to attempt deletion or wait for implementation. No explicit when-to-use or when-not-to-use criteria are given.

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