List Domains

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered by structured data. The description adds only the scoping fact that results are custom domains of one Cube; it says nothing about pagination, empty results, or whether pending/unverified domains are included.

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?

A single sentence with no filler, and the resource and its scope are front-loaded. Nothing could be removed without losing 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?

For a two-parameter read tool with full schema coverage and read-only annotations, the definition is minimally sufficient. With no output schema, however, it should hint at what a listed domain contains (records, verification state) to set expectations for downstream calls like get_domain_records.

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 100%, with both cubeId and spaceId documented in the input schema, so the baseline is 3. The description adds no meaning beyond the schema, such as what happens when spaceId is omitted or how an invalid cubeId is handled.

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 a specific verb and resource ("List the custom domains") scoped to a parent ("attached to a Cube"), which is more precise than the bare title. It does not differentiate itself from nearby siblings such as get_domain_records or list_cubes, but the list-domains intent is unambiguous.

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?

Usage is only implied: an agent infers it should call this when it has a cubeId and wants its domains. No alternatives (get_domain_records, list_cubes) or exclusions are named, and no prerequisites such as spaceId defaults or domain-state conditions are mentioned.

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