Create HTTPS Record

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

Beyond annotations (destructiveHint=true), the description details the exact destructive behavior ('overwritten, not merged') and the prerequisite check, adding valuable behavioral context not captured in annotations alone.

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?

Three sentences total: purpose statement, use-case context, and a critical warning. No filler language; every sentence adds value and key information is front-loaded.

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 creation tool with 8 parameters and no output schema, the description covers the core behavior (overwriting) and prerequisite. Missing details about return values or error handling, but the annotations compensate for safety profile, making it adequately complete.

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 parameter descriptions already present; the description does not add significant new insight into individual parameters beyond the schema, thus baseline score 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 states 'Create an HTTPS record (SVCB-compatible for HTTPS) for a domain' with specific use cases ('HTTPS service binding and ECH'), clearly distinguishing this from other record creation tools among 40+ siblings.

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?

Explicitly warns that this tool 'replaces ALL existing HTTPS records with the same name' and advises to 'Use list_dns_records first to check for existing records,' providing clear when-to-use and when-not-to-use guidance.

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