kql_database_get_definition

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 covered. The description adds 'long-running' as a genuinely useful behavioral trait, but the file-write sentence largely restates the outputDirectoryPath schema description rather than disclosing new behavior such as overwrite rules or completion signaling.

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 short and front-loads the core purpose. It loses a point because the second sentence partly duplicates the schema description for outputDirectoryPath instead of contributing new 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 three simple, fully described parameters this is adequate, but the lack of an output schema makes the 'long-running' note vague: the agent is not told what the call returns, how to detect completion, or what files are produced. That is a meaningful gap for an export-style tool.

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?

Schema coverage is 100%, so the schema already documents all three parameters. The description adds no new meaning beyond the property descriptions; it mentions the output directory but does not clarify file naming, format, or overwrite behavior.

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 first sentence names a specific verb ('Get') and resource ('definition of a KQL database'), so an agent can immediately see the target. The 'long-running' qualifier and the file-write mechanism add useful scope, though it does not explicitly differentiate itself from the sibling kql_database_get.

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 when-to-use or when-not-to-use guidance is provided. The description does not mention alternatives like kql_database_get for quick reads, nor does it state prerequisites such as whether the output directory must already exist or how long the operation may take.

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