Delete Domain

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

Annotations already mark this as destructive (destructiveHint=true). The description adds valuable context by specifying that links using this domain will stop working and that the action is irreversible, going beyond the annotation to describe the specific impact.

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 two short sentences, front-loaded with the action and consequence. Every sentence adds value with no repetition.

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 tool has a single parameter, no output schema, and a clear destructive annotation, the description sufficiently covers the action, its effect on links, and irreversibility. It doesn't mention return values, but that's minor for a delete operation.

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 already documents the only parameter, domainId, as a UUID identifier. Schema coverage is 100%, so the description does not need to add parameter details. The description adds no additional semantic information about the parameter itself, 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?

Description clearly states the tool removes a custom domain from a ULink project. The verb 'Remove' and resource 'custom domain' distinguish it from sibling tools like add_domain, verify_domain, and list_domains.

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 provides context that removing a domain will stop any links using it and that the action is irreversible, helping the agent understand when to use it. It does not explicitly name alternatives or exclusions, but the warning implies careful usage.

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