kusto_query

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds that it returns results as a list of dictionaries, which is basic. No additional behavioral traits (e.g., rate limits, error behavior) are disclosed, but nothing contradicts 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?

The description is concise with a clear purpose statement followed by a structured docstring listing parameters. It avoids extraneous text, though the docstring format is slightly redundant with the input schema.

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 that annotations cover safety and output schema exists, the description adequately explains the core purpose and key parameters. It does not address edge cases like timeouts or authentication, but for a straightforward query tool, it's reasonably complete.

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 0%, so description must compensate. It provides brief meanings for each parameter (e.g., 'The KQL query to execute'), which adds value over bare names. However, it lacks format details or constraints, making it merely adequate.

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 clearly states 'Executes a KQL query on the specified database,' which provides a specific verb (Executes) and resource (KQL query on database). This distinguishes it from siblings like 'kusto_command' (admin commands) and 'kusto_describe_database' (describing metadata).

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 explicit guidance on when to use this tool versus alternatives. It mentions fallback to default database but does not contrast with other query or data tools, leaving the agent without decision context.

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