analyze_slow_queries

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

With no annotations, the description bears full responsibility for disclosing behavioral traits. 'Find' implies a read operation, but there is no explicit statement about safety, mutability, or side effects. The tool's behavior regarding data retrieval or performance impact is unclear.

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, which is concise, but it omits critical information such as return value and parameter interaction. It is structured as a brief statement, but the brevity sacrifices clarity for completeness.

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 7 parameters, no output schema, and no annotations, the description is insufficient. It does not explain what the tool returns (e.g., list of queries with execution times), how parameters combine (e.g., requestId vs. count), or what 'slow' means beyond the threshold parameter.

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?

All 7 parameters have schema descriptions (100% coverage), so the baseline is 3. The tool's description adds little beyond the schema, only referencing 'threshold' which is already documented. The interplay between parameters (e.g., count vs. since) is not explained.

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 'Find slow database queries above threshold' clearly states the tool's action (finding) and resource (slow database queries), which is specific enough. However, it does not explicitly differentiate from sibling tools like 'get_queries' or 'get_query_stats', missing an opportunity to highlight its unique purpose.

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 usage guidance is provided. The description gives no indication of when to use this tool versus alternatives (e.g., 'get_queries' for all queries, or 'detect_n_plus_one' for N+1 problems). Missing exclusions or recommended contexts.

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