get_longest_running_queries

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

Annotations already declare readOnlyHint=true, so the tool is known to be safe. The description adds valuable context by specifying the source catalog ('system:completed_requests'), indicating that the queries are completed, not currently running. However, it does not clarify how 'longest running' is defined (e.g., duration) or mention ordering.

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 a single sentence of 12 words, conveying the essential information without any unnecessary words. It is perfectly concise and well-structured.

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 tool's simplicity (1 optional parameter, no required inputs, an output schema exists), the description is sufficiently complete. It identifies the data source and the purpose. The presence of an output schema means return values need not be described.

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% (the only parameter 'limit' is fully described in the schema). The description does not add additional semantic meaning beyond what the schema provides; it only restates the parameter implicitly by saying 'N'.

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 it gets the N longest running queries from a specific catalog (system:completed_requests). The verb 'Get' and resource 'longest running queries' are specific. The phrase 'longest running' distinguishes it from sibling tools like get_most_frequent_queries or get_queries_with_largest_response_sizes.

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 implies usage for retrieving long-running queries from the completed requests catalog, but it does not provide explicit guidance on when to use this tool versus its siblings (e.g., get_most_frequent_queries, get_queries_not_selective). No exclusions or alternatives are mentioned.

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