domains_delete_glue_record

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

The annotation destructiveHint=true already communicates the destructive nature, but the description adds no additional behavioral context. It does not mention irreversibility, DNS impact, or permission requirements. With annotations present, the bar is lower, but the description still fails to disclose any non-obvious behavior.

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, highly concise and front-loaded. It contains no irrelevant information and directly states the action. Every word earns its place, making it an exemplar of conciseness.

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 complete schema and destructive annotation, the description is adequate for a simple delete operation. However, it lacks usage context, does not explain what a glue record is, and omits the consequences of deletion. The presence of an output schema would cover return values, but the description still leaves some contextual gaps.

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 input schema covers both parameters (domain and subdomain) with descriptions at 100% coverage. The tool description itself does not elaborate on these parameters, but the schema provides complete meaning. A baseline score of 3 is appropriate because the schema does the heavy lifting.

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 uses a specific verb 'Delete' with a clear resource 'glue record', distinguishing it from sibling tools like domains_create_glue_record and domains_update_glue_record. However, it closely mirrors the tool name without adding extra context, so it lacks the richness of a top-tier purpose statement.

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 guidance is provided. The description does not mention when to use this tool versus alternatives, nor does it list prerequisites or exclusions. While the existence of sibling glue record tools implies context, the description itself offers no explicit direction.

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