ss_domains

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

No annotations provided. Description implies a read-only listing operation but doesn't explicitly state non-destructive nature, rate limits, or authorization requirements. Adequate but minimal for a list operation.

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 that is concise and front-loaded with the key action. No unnecessary 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?

No output schema. Description doesn't mention return fields or format. For a simple paginated list, it's somewhat complete but could describe what domain information is returned.

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 fully describes both parameters (take, skip) with descriptions. The description adds only 'paginated' which is already implicit from the schema. Baseline score of 3 with no additional value.

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 'List all domains in your Spaceship account (paginated)', providing a specific verb and resource. It distinguishes from sibling tools like 'ss_domain_info' (single domain) and 'ss_domains_check' (domain availability).

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?

No guidance on when to use this tool versus alternatives. The word 'paginated' hints at pagination usage but doesn't explain when to prefer this over other domain-related tools like 'ss_domain_info' for specific domains.

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