kql_database_get

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

The annotations already declare readOnlyHint=true and destructiveHint=false, and the description simply says 'Get details' without adding behavioral context such as what data is returned, whether it returns full metadata, or how it differs from kql_database_get_definition. No contradiction exists, but the description contributes no behavioral transparency beyond the annotations.

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, focused sentence of nine words with no filler. Every word contributes meaning, and the core action and target resource are front-loaded.

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?

This is a minimal description for a simple tool, but there is no output schema and no explanation of what 'details' includes. Given the sibling kql_database_get_definition, the agent could be uncertain whether this returns metadata, configuration, or the full definition. More context is needed to disambiguate the return value.

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 describes both parameters with 100% coverage: 'The workspace ID' and 'The KQL database ID.' The description adds no additional parameter semantics, so it correctly relies on the schema. Baseline 3 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 uses a specific verb and resource: 'Get details of a specific KQL database.' This clearly conveys a read operation targeting one database, and the word 'specific' helps distinguish it from kql_database_list. However, it does not explicitly differentiate from kql_database_get_definition, so it is not a perfect 5.

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 given about when to use this tool instead of siblings such as kql_database_list or kql_database_get_definition. The description implies a single-resource lookup but offers no explicit context, exclusions, or alternative routing.

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