ado_query_analytics

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

Annotations indicate readOnlyHint=true, and description uses 'Query' which is consistent. It adds context about OData capabilities (filtering, aggregation) beyond the annotation, but doesn't detail response format or pagination.

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?

Two concise sentences: first states purpose, second lists entity sets and supported operations. No wasted words, front-loaded with key information.

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 input capabilities well but doesn't describe the response format or behavior beyond OData operations. However, the tool's purpose as a query is clear, and the schema covers parameter constraints like top maximum.

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?

High schema coverage (86%) as baseline (3). The description adds value by giving examples of common entity sets and listing supported OData operators, which enriches understanding of how to use entitySet and query 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 clearly states the tool queries the Analytics OData feed for reporting, lists common entity sets, and distinguishes from sibling tools like ado_get_analytics_metadata which deals with 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?

It explicitly lists supported OData query options ($filter, $select, etc.) which helps the agent decide when to use this tool for analytics. No explicit contrast with alternatives, but the specific options provide enough guidance.

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