kusto_deeplink_from_query

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

Annotations already indicate read-only and non-destructive nature. The description adds behavioral details: cluster type auto-detection, fallback to .show version, and that it returns None on failure. No contradictions.

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?

Description is clear and front-loaded with purpose. Parameter docs are structured but could be integrated more compactly. Still concise overall.

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?

Covers purpose, cluster detection, fallback, parameters, and return. For a simple URL-building tool with an output schema, this is fully 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 provides only titles. Description adds parameter descriptions (cluster_uri, database, query) and return value. This adds significant meaning beyond the schema, though could include format or encoding details.

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 explicitly states it builds a deeplink URL for a KQL query, specifying different target UIs for Azure Data Explorer and Fabric. This clearly distinguishes it from sibling tools like kusto_query that execute queries.

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 explains when to use (to open a query in a web UI) and the auto-detection fallback behavior. It does not explicitly list alternatives, but the context from sibling tools makes it clear when not to use.

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