Analyze workload

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

The description discloses that the tool depends on the pg_stat_statements extension and reports availability=false if not installed, adding behavioral context beyond the readOnlyHint annotation. It does not detail every behavioral aspect but is sufficient given annotations.

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 succinct sentences plus an example, front-loaded with key information. Every sentence adds value, achieving high efficiency.

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?

The description covers the tool's core functionality, dependency on an extension, and availability behavior. With an output schema present, explanation of return values is unnecessary, making the description 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?

Schema coverage is 50% with only the database parameter described. The description provides an example using the limit parameter but no further semantics. Baseline is 3 due to coverage, and the description adds only marginal value beyond the schema.

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 returns the slowest queries by mean execution time, a specific verb+resource. It distinguishes from sibling analysis tools by focusing on workload via pg_stat_statements and explicitly mentions the availability flag when extension is missing.

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 indicates usage for identifying slow queries with an example syntax, providing clear context. However, it does not explicitly state when not to use this tool or mention alternatives among the many sibling analyze tools.

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