Performance Query Log

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

No annotations are provided, so the description carries the full behavioral burden, and 'Get slow query log' discloses nothing about the log's source (MySQL slow log vs. Drupal watchdog), required permissions, whether results are paginated, or ordering. For a diagnostic read tool with zero annotation coverage this is a real gap.

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?

One short front-loaded sentence with zero waste, but at this length it is under-specified rather than genuinely concise for a tool with no annotations and two undocumented parameters.

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?

An output schema exists, so return values need not be explained, but with no annotations, 0% schema coverage, and no stated log source or filtering semantics, an agent cannot confidently call this tool. The description is too thin for a diagnostic query tool.

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 0% and the description says nothing about either parameter. The names limit and min_duration are semi-self-explanatory, but critical details like the unit for min_duration (seconds vs. milliseconds) and the meaning of limit=0 or its default of 100 are undocumented anywhere.

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?

States a specific verb and resource ('Get slow query log'), so an agent knows this returns slow-query data rather than general DB results. It does not distinguish itself from adjacent siblings such as db_query, drush_watchdog, or performance_page_load_analyze, which is the only thing keeping it from a 5.

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?

There is no guidance on when to reach for this tool versus db_query, drush_watchdog, or the other performance_* tools. No prerequisites (e.g., which log source must be enabled) and no exclusions are stated.

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