ClawDaddy MCP Server

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

No annotations provided, so description carries full burden. Clarifies authentication requirement ('management token') and read-only nature via 'Get', but omits error behaviors, caching, or return value structure.

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 efficiently structured: function (get domain settings) followed by constraint (requires management token). No redundant words, properly front-loaded.

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?

Appropriate for a simple 2-parameter retrieval tool. Lists specific settings retrieved, partially compensating for missing output schema. Lacks return format description but covers core functionality and auth requirements adequately.

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% with complete parameter descriptions. Description adds clarification that token is a 'management token', aligning with schema's 'clwd_' prefix hint, but does not elaborate on domain format or token acquisition.

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?

States specific verb 'Get' and resource 'domain settings', enumerating exact setting types (lock status, auto-renew, privacy). Implicitly distinguishes from update_settings (read vs write) and DNS tools, though could explicitly contrast with get_domain_info.

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?

Provides prerequisite guidance ('Requires management token') indicating when tool is usable, but lacks explicit when-to-use guidance versus siblings like get_domain_info or update_settings.

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