delete_service_domain

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'Remove' without revealing whether the action is irreversible, requires specific permissions, or what happens if the domain is still in use. This is a gap for a delete operation, similar to the update_drive example.

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 sentence that is front-loaded with the action and resource. There is zero wasted text; every word is essential.

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 simple delete operation with well-described parameters, the description is minimal but adequate. However, the absence of behavioral context (reversibility, prerequisites) and usage guidance means it is not fully complete. The lack of an output schema also leaves return behavior unspecified, though this is not strictly required.

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 provides descriptions for both serviceId and environmentId (100% coverage), so the baseline is 3. The description adds no additional parameter-specific meaning beyond clarifying that the domain is Railway-provided, which is more about purpose than parameter semantics.

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 'Remove' and clearly identifies the resource as 'the Railway-provided domain from a service'. This not only states the action but also distinguishes the tool from siblings like create_service_domain or create_custom_domain, which involve adding 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 implies the tool is used when you want to remove the Railway-provided domain from a service, but it does not explicitly state when not to use it or mention alternatives such as create_custom_domain for custom domains. No exclusions or edge cases are provided.

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