profiles_list_domains

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

No annotations are provided, and the description only states 'List profile domains.' It does not disclose whether the operation is read-only, how pagination works, or if auth/session is required. The description adds no behavioral context beyond the simple verb 'List'.

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 three-word sentence with absolutely no wasted words. It is front-loaded and to the point, though it is perhaps too terse to be fully useful.

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?

Although an output schema exists, the description is too sparse to be considered complete. It lacks any context about the domain model, parameter behavior, or differentiation from similar list tools, making it difficult for an agent to use correctly.

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 defines a single parameter max_results with 0% description coverage, and the tool description does not mention it at all. The agent gets no explanation of what max_results controls or how to use it, so the description adds zero value beyond the schema's default 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?

The description uses the specific verb 'List' and resource 'profile domains', making the basic purpose clear. However, it does not explain what a profile domain is or differentiate from sibling list tools like list_domains_for_instance or cases_list_domains, so it lacks full scope.

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 does not mention any context, prerequisites, or situations where another tool should be preferred, leaving the agent to infer usage solely from the name.

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