Remove Custom Portal Domain

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

Annotations indicate destructiveHint=true and readOnlyHint=false, which the description supports by stating removal. The description adds that the portal reverts to the default subdomain, but does not disclose potential side effects, reversibility, or error states. With annotations already conveying destructiveness, the description provides some added context but not extensive.

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 very concise, using two sentences in English and repeating in Spanish. It is front-loaded with the action and outcome, with no unnecessary information.

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's simplicity (one parameter, no output schema), the description covers the essential purpose and effect. It could be improved by mentioning the expected behavior for invalid domains or success confirmation, but is adequate for basic use.

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 schema covers the single parameter with a description. The description provides a concrete example (domain='portal.miempresa.com') which clarifies the expected format beyond the schema's text. Schema coverage is 100% but the example adds significant value.

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 (remove a custom domain) and the result (revert to default subdomain). It provides an example. However, it does not explicitly differentiate from sibling tools like add or verify, though the verb 'remove' makes it distinct.

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 explicit guidance on when to use this tool vs. alternatives. The description implies it is for removing a previously added domain, but does not mention prerequisites, when not to use, or relationship to other portal domain tools.

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