cases_list_domains

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

No annotations are provided, so the description must convey behavior. It only states 'list' without disclosing details like pagination, filtering behavior via region, result limits, or whether the operation is read-only. The agent gets no insight into side effects or response characteristics.

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?

The description is extremely short and front-loaded, containing no fluff or redundant phrasing. However, its brevity borders on under-specification, though this is not a matter of excessive length or poor structure.

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?

With two optional parameters, a vague resource concept, and an output schema present, the description is far too minimal. It does not clarify what constitutes a 'case domain', how region filters results, or what max_results controls, leaving the agent without sufficient context for correct invocation.

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 description coverage is 0%, and the description does not mention parameters at all. The agent only sees parameter names 'region' and 'max_results' with defaults and types, but no explanation of their purpose or expected values, forcing guesswork.

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 'List case domains' uses a specific verb (list) and resource (case domains), making the core action clear. It differentiates from sibling tools like cases_create_domain and cases_get_domain, though it does not distinguish from other domain-listing tools such as list_domains_for_instance or profiles_list_domains.

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?

There is no guidance on when to use this tool versus alternatives. The description omits any context about scenarios, prerequisites, or distinctions from similar domain-listing tools, leaving the agent without decision support.

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