Create monitors from a JSON structure (typically produced by export). Skips domains the user is already monitoring; honors the plan's domain limit. Returns a per-domain status.
| Name | Required | Description | Default |
|---|---|---|---|
| payload | Yes | Export payload, version 1.0. Use the `export` tool to generate one. |
| Name | Required | Description | Default |
|---|---|---|---|
| added | No | ||
| results | No | Per-domain import status. | |
| requested | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations indicate idempotentHint=true and readOnlyHint=false. The description adds context about skipping existing domains and honoring plan limits, which is beyond what annotations alone provide. It does not contradict 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?
Three sentences, each essential: action, behavior details, return value. Front-loaded with the main purpose. No wasted words.
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 a single parameter with full schema coverage and an output schema, the description fully covers: what the tool does, how to produce input, behavioral nuances (skip existing, limit), and return format ('per-domain status'). No gaps.
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?
Schema coverage is 100% (single parameter with description). The description adds value by specifying 'Export payload, version 1.0. Use the `export` tool to generate one,' which clarifies provenance and format.
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 verb 'Create monitors' and the resource 'from a JSON structure (typically produced by `export`).' This distinguishes it from sibling tools like add_monitor (single monitor) and export_monitors (export).
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: it imports from an export payload and mentions specific behaviors (skips existing domains, honors plan limit). However, it does not explicitly state when not to use it or list alternative tools for adding monitors individually.
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.
Tools are mostly distinct but some overlap exists between add_monitor/add_monitors (batch vs single) and export_monitors/list_monitors (export vs list). Descriptions help disambiguate, but an agent might initially confuse export_monitors with list_monitors.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., add_monitor, create_certificate, list_monitors). No mixed conventions or vague verbs.
17 tools is reasonable for a TLS monitoring and certificate management server. Each tool serves a distinct function without significant bloat, though the deprecated register_beacon_order could be removed.
Covers core CRUD for monitors, certificate lifecycle (create, check propagation, finalize, renew, status, scan), account info, and team invites. Minor gaps: no batch remove_monitors, no monitor update, and no detailed certificate inspection beyond status.
