azure_query

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

No annotations are provided, so the description carries the full burden. It only states 'run a query,' implying read-only behavior, but does not explicitly confirm non-destructiveness, rate limits, authentication requirements, or failure handling. The schema covers parameters but not runtime behavior.

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?

Single sentence, front-loaded with purpose. Efficient with no wasted words. However, it could be slightly restructured to include usage hints or formatting for clarity. Still above average.

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?

No output schema is provided, so the description should explain return values or result format, but it does not. For a complex tool involving Kusto queries, users need examples, constraints on query complexity, or hints about result limits. The description is too minimal.

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 description coverage is 100%, so baseline is 3. The description adds no extra meaning beyond the schema. The schema itself describes the query, timespan, and workspace_id parameters adequately. The tool name and description already imply the query parameter.

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 the tool runs a custom Kusto query on Application Insights logs, using a specific verb and resource. It distinguishes from sibling tools like azure_requests or azure_metrics, which are pre-defined for specific data types, by emphasizing custom 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?

No guidance on when to use this tool versus the pre-defined sibling tools. An agent would not know whether to use azure_query or a specialized tool like azure_requests for specific tasks. No exclusion criteria or alternative suggestions are provided.

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