dnsimple_list_domainsList the domains in the account, with pagination and optional filters. API: GET /{account}/domains.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number (1-based). | |
| sort | No | Sort order, e.g. "name:asc", "expiration:desc", "id:desc". | |
| per_page | No | Results per page (max 100). | |
| name_like | No | Filter to domains whose name contains this substring. | |
| registrant_id | No | Filter to domains with this registrant (contact) id. |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide readOnlyHint=true, so description is consistent. Description adds value by disclosing pagination and filtering behavior and providing the API endpoint. No contradictions.
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?
Single sentence plus API path, front-loaded with key action and parameters. No wasted words; every part 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?
For a list tool with no output schema, description adequately explains purpose and features. Lacks details on return format but sufficient given low complexity.
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%, so baseline is 3. Description adds general context (pagination and filters) but does not elaborate on specific parameter formats beyond what schema already provides.
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?
Description clearly states action 'list', resource 'domains in the account', and mentions pagination and optional filters. Distinguishes from siblings like dnsimple_get_domain (single domain) and dnsimple_check_domain.
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?
Description implies usage for listing all domains but does not explicitly state when to use vs alternatives (e.g., dnsimple_get_domain for a single domain). Lacks when-not or alternative guidance.
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.