list-me-domains

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

Annotations provide readOnlyHint=true (mutation safety) and openWorldHint=true (dynamic results). The description adds that it supports pagination and filtering, which is useful behavioral context beyond annotations. It discloses the purpose for discovering domain IDs. 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?

Three sentences: purpose, supported features, usage hint. No filler or redundancy. Front-loaded with the primary action. 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 low complexity (list with filters), no required params, and no output schema, the description adequately covers purpose, filtering, pagination, and usage hint. Minor gap: doesn't mention the range of states explicitly (but schema does), and doesn't describe return format (acceptable without output schema).

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?

Input schema covers 100% of parameters with descriptions, so baseline is 3. The description adds value by clarifying that fqdn is an 'Exact FQDN match filter' and that 'When set, only that domain is returned', which reinforces behavior. The state filter is explained with examples. This raises the score to 4.

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 'list' and the resource 'domains owned by the authenticated account'. It distinguishes from sibling tools like 'get-me-domain' (single domain) and 'search-domains' (broader search) by specifying the scope and filtering options.

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 includes a usage hint: 'Use this to discover domain IDs needed by other tools (e.g. DNS management).' This provides context for when to use this tool. However, it does not explicitly exclude cases or mention alternatives beyond the hint, so it scores a 4.

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