Remove one or more domains from this account's trusted allowlist.
Once removed, those domains resume normal scoring on the next check. Use list_allowlist to see what is currently on the list before removing.
| Name | Required | Description | Default |
|---|---|---|---|
| domains | Yes | Registrable domains to remove (e.g. ['partnerco.com']) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With annotations already marking the operation as non-read-only, non-destructive, and idempotent, the description adds useful context: removal causes domains to 'resume normal scoring on the next check.' This explains the consequence and timing without contradicting the annotations.
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?
Two concise sentences: the first states the action, the second explains the effect and offers a helpful precursor step. No wasted words, and the structure front-loads the core purpose.
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, single-parameter tool with complete annotations and no output schema, the description covers the action, consequence, and a usage recommendation. Nothing essential is missing.
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 provides full documentation for the 'domains' parameter (description, constraints, examples). The description's phrase 'one or more domains' adds no new parameter-level meaning. Given 100% schema coverage, the baseline of 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 clearly states the action: 'Remove one or more domains from this account's trusted allowlist.' It uses a specific verb (Remove) and resource (allowlist), and differs from sibling tools like add_to_allowlist and list_allowlist.
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 clear context by recommending using list_allowlist before removal, but it does not explicitly mention when not to use the tool or alternatives beyond the implicit inverse of add_to_allowlist. This is strong guidance but falls short of explicit when/when-not coverage.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have clearly distinct purposes: check_url vs check_urls distinguish single vs batch, allowlist CRUD tools are separated, and profile management is distinct from account billing. Minor overlap exists between get_balance and get_stats (both report balance) and between list_profiles and show_defaults (both relate to scoring configuration), but descriptions clarify the differences.
The vast majority of tools follow a verb_noun snake_case pattern (check_url, create_profile, list_allowlist, get_balance). A few outliers like purchase and signup are single verbs, but they are standard and do not break the overall predictability.
18 tools is above the ideal 3-15 range but appropriate for the server's broad scope: URL analysis, custom scoring profiles, allowlist management, account billing, and reporting. Each tool serves a distinct function and none feel redundant or superfluous.
The tool surface covers the core domain thoroughly: single and batch URL checks, credit estimation, profile CRUD (create, list, delete, show defaults), allowlist CRUD, history, and account management (signup, balance, pricing, purchase). Minor gaps exist, such as no delete history or direct retrieval of a single past check by ID, but these are not critical.