execute-query

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

With no annotations, the description carries full burden. It discloses the default row limit, the ability to override it, and the significance of partial results. This is good transparency for a query tool, though it does not mention idempotency or read-only nature (implied but not explicit).

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?

Three sentences, each essential. The first states the main action, the second explains the default limit and how to change it, the third advises on partial results. No filler or redundancy. Properly 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?

Given no output schema, the description explains the result limit and partial result handling. It is missing information on error handling, authentication, or query syntax specifics, but for a simple query tool, it covers the key behavioral aspects needed for correct usage.

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%, with descriptions for both 'query' and 'limit'. The description adds context: 'By default, limits results to 20 rows to prevent context overflow. Use the 'limit' parameter to specify a different maximum.' This goes beyond the schema's 'Maximum number of rows (default: 20)' by explaining why the default exists and how to adjust.

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 'Runs KQL queries and returns results,' specifying the verb ('Runs') and resource ('KQL queries'). It distinguishes from sibling tools like 'show-table' and 'initialize-connection', which serve different purposes. The purpose is unambiguous and specific.

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 description provides guidance on default behavior ('limits results to 20 rows'), how to adjust via the limit parameter, and what to do with partial results (revise query with aggregations). However, it does not explicitly state when to use this tool versus alternatives (e.g., show-table for schema), but context is clear enough for typical use.

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