mirrored_database_list

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

Annotations already establish the operation is read-only and non-destructive, lowering the bar. The description adds workspace scoping and the 'all' enumeration behavior, but it does not disclose return format, pagination, or any additional behavioral traits.

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?

One short sentence carries the operation, resource, and scope with no filler. It is front-loaded and easy to parse.

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 one-parameter, read-only list operation, the description is mostly complete: it names the action, resource, and required scope, and list semantics imply a returned collection. It lacks only an explicit note about what each listed item contains, which would be useful without an output schema.

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 input schema provides 100% coverage for the only parameter, workspaceId, so the description is not required to compensate. The phrase 'in a workspace' simply restates the parameter's purpose without adding format, constraints, or usage detail.

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 precise verb ('List'), names the resource ('mirrored databases'), and scopes it to a workspace. The 'all' phrasing distinguishes it from single-item tools like mirrored_database_get and from list tools for other resource types such as kql_database_list.

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 wording implies this is the correct tool when an agent needs to enumerate every mirrored database in a given workspace. However, it does not explicitly say when to prefer it over alternatives or mention the single-resource counterpart (mirrored_database_get).

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