get_slow_queries

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

Because there are no annotations, the description carries the burden of behavioral disclosure. It does disclose sorting behavior by total execution time, but it does not mention read-only nature, response shape, limits, pagination, or thresholds beyond what the schema already captures.

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?

It is a single sentence with no filler. It is front-loaded with what the tool does and adds a useful sort detail without unnecessary branching or repetition.

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?

For a simple two-optional-parameter read-style list tool, the description is adequate and the schema fully documents parameters. However, the return format is not specified, and because no output schema or annotations exist, slightly more detail about what each returned query looks like would make it more 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?

The schema provides complete description for both parameters (limit and minDurationMs), so the description's additional value is naturally limited. The description does not explain parameter semantics beyond the schema, and the sort-order hint is not targeted at individual 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 names a specific resource and operation: getting slow database queries sorted by total execution time. This clearly describes the tool's result, but it does not explicitly contrast it with related database siblings such as get_database_metrics or get_table_stats.

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 phrase 'that may need optimization' implies this is used in performance tuning. However, it does not explicitly state when to pref on analytics or metrics. No exclusions or alternative-method guidance is provided.

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