account_metastores_create

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

The description only repeats the action 'create'. Annotations indicate readOnlyHint=false, but no additional behavioral traits are disclosed (e.g., idempotency, permissions, side effects). With only readOnlyHint, the description adds negligible transparency.

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 sentence, very concise. However, it lacks structure (e.g., no parameter descriptions or usage context). It is appropriately short but could be more informative.

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 the tool's complexity (nested object parameter, output schema exists, account-level operation), the description is severely lacking. It does not explain return values, prerequisites, or how to construct the body, making it incomplete.

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 single parameter 'body' has a vague description 'Metastore creation body' and allows additionalProperties: true. The tool description provides no further detail on expected keys or structure, offering no value beyond the schema.

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 'Create a Unity Catalog metastore' clearly states the verb and resource. It distinguishes from sibling account_metastores_* tools which are for other CRUD operations. However, it does not specify that this is at the account level or clarify 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?

No guidance is provided on when to use this tool versus alternatives, prerequisites, or when not to use it. The description lacks any contextual advice.

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