account_metastores_list

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

The description is consistent with the annotation readOnlyHint=true, but adds no additional behavioral context beyond what the annotation already conveys. It does not disclose any potential limitations, pagination, or ordering details.

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 single-sentence description is extremely concise and directly states the tool's purpose with no extraneous 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 simple listing tool with no parameters and an output schema present, the description covers the essential purpose. It is complete enough given the tool's simplicity and the annotations providing safety context.

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 tool has zero parameters and the schema description coverage is 100%. The description adds no parameter details, which is acceptable since there are none to describe. Baseline 4 applies.

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 explicitly states 'List Unity Catalog metastores under the account,' providing a specific verb ('List'), resource ('Unity Catalog metastores'), and scope ('under the account'). It clearly distinguishes from sibling tools like account_metastores_create, _delete, _get, and _update.

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 for listing metastores, but does not provide explicit when-to-use or when-not-to-use guidance or mention alternatives. The context of sibling tools suggests its role, but explicit guidance is absent.

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