get_domains

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

With no annotations provided, the description relies entirely on itself, and it is extremely brief. It fails to disclose critical behavioral traits like pagination limits, common constraints on 'cloud policy,' or whether the returned list is comprehensive.

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, well-formed sentence. It is perfectly concise and front-loads the most critical information—the resource and its specific scope—without any unnecessary fluff.

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?

Given that it takes no parameters, the description defines the scope well. However, because it is a 'list' tool, it is not fully complete; it would benefit from clarifying if this is a paginated list or if there are default filtering criteria for 'cloud policy' adherence.

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?

Since the tool takes zero parameters, the input schema coverage is 100%. Per the rules, the baseline score of 3 applies, as the description adds no additional semantic meaning to the zero required inputs.

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 a specific verb ('List') and resource ('Keystone domains'). It distinguishes itself by adding a vital scope constraint: 'subject to cloud policy,' which sets it apart from generic domain listings among its many siblings.

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 implies usage by stating what the list includes, but it does not explain when to use this specific tool versus another listing tool (e.g., a more general 'get_keystone_domains'). The usage is simply implied by the need to query policy compliance.

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