list_domains_for_instance

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

With no annotations provided, the description carries the full burden. 'List' implies a read operation, but there is no mention of what data is returned, how many results, ordering, or error behavior, and it does not clarify whether this is purely a read operation with no side effects.

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 a single, concise sentence that directly states the operation and its scope. Every word contributes, and there is no redundant information.

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?

The tool is relatively simple and has an output schema, but the description alone is sparse. It doesn't clarify how it differs from 'cases_list_domains' or what 'case domains' means, nor does it explain the role of max_results; the contextual completeness is adequate only for the most basic understanding.

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?

The schema has 0% description coverage, and the description does not mention instance_id or max_results at all. While instance_id is self-evident from the tool name and description, max_results—which limits the number of returned domains—is completely absent, leaving the agent guessing about its semantics.

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 uses the specific verb 'List' and identifies the resource 'case domains' scoped to a particular Connect instance. This clearly distinguishes it from sibling tools like 'cases_list_domains' or 'profiles_list_domains' which imply different scopes.

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 provides clear context—this is for listing case domains belonging to a specific instance. However, it does not explicitly discuss alternatives or exclusions, leaving the agent to infer that other domain-list tools exist.

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