execute_query_external_table

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

The description does not disclose whether the tool is read-only or modifies data, nor does it mention required permissions, error handling, or any side effects. With no annotations, the description carries the full burden, but it provides almost no behavioral context beyond 'execute'.

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 only 5 words, which is extremely concise, but it sacrifices essential information. It fails to earn its place as a helpful guide; instead it is under-specified.

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 the absence of an output schema, annotations, and any additional context, the description is wholly inadequate. It does not explain what 'external table' means, what the query returns, or how this tool differs from siblings, making it nearly useless for an AI agent.

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?

With 0% schema description coverage, the description must explain the parameters. It only lists 'database' and 'query' by name, adding no meaning about allowed values, formats, or constraints. The schema provides no descriptions either, so the AI has no guidance on how to properly fill these parameters.

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 states 'Execute a kql query to external table', which identifies the action (execute) and the target (external table), but is vague about the nature of the query and lacks detail that would distinguish it from similar tools like execute_query_internal_table. The term 'kql' is likely a typo for 'KQL' but assumes domain knowledge.

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 provided on when to use this tool versus its siblings (e.g., execute_query_internal_table). There is no mention of prerequisites, restrictions, or context in which this tool is appropriate, leaving the AI agent to infer usage from the name alone.

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