kql_database_list

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is established. The description adds that it lists 'all' databases within a workspace, which is useful scoping, but it does not disclose any return format, pagination behavior, or error conditions beyond what the annotations already imply.

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?

A single, short sentence that states the operation, resource, and scope with zero filler. The key action ('List') and target ('KQL databases') are front-loaded, making it immediately scannable by an agent.

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, read-only list operation with one fully documented required parameter, the description is sufficient for correct invocation. The absence of an output schema is acceptable because the word 'List' already implies the return value is a collection of KQL databases.

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 has 100% coverage of the single parameter 'workspaceId' with the description 'The workspace ID'. The tool description does not add further parameter-level meaning, but it also does not need to since the schema fully documents the only required input.

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'), a specific resource ('KQL databases'), and a scoping context ('in a workspace'). This clearly distinguishes it from sibling tools like kql_database_get, kql_database_create, and list tools for other resource types.

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 intended use is implied: call this when you need to enumerate all KQL databases in a given workspace. However, there is no explicit mention of when not to use it or alternatives such as kql_database_get for a single database, so the guidance is not fully explicit.

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