Delete a custom scoring profile. This is permanent. Any future check requests using this profile name will fall back to default weights.
Use list_profiles to see your current profiles before deleting.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Name of the profile to delete |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate destructiveHint:true and idempotentHint:true. The description adds valuable context beyond annotations: it states deletion is permanent and that future requests using the profile name will fall back to default weights. This fully discloses the behavioral 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 sentences: the first states the action and permanence, the second gives usage guidance. It is front-loaded, concise, and every sentence earns its place.
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 param, no output schema) and comprehensive annotations, the description covers all necessary aspects: what it does, permanence, fallback behavior, and prerequisite guidance. No gaps remain.
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 description coverage is 100%—the only parameter 'name' is already described as 'Name of the profile to delete' with a pattern. The description adds no additional parameter semantics beyond what the schema provides, so the baseline 3 applies.
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 'Delete a custom scoring profile', which is a specific verb and resource. It also differentiates from siblings like list_profiles and create_profile by focusing on deletion. The permanent nature and fallback behavior further reinforce the action.
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 explicitly advises 'Use list_profiles to see your current profiles before deleting', providing a clear prerequisite. It also explains the consequence of deletion ('fall back to default weights'), which helps the agent decide when this tool is appropriate.
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.