pg_kill_query

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

With no annotations, the description must disclose behavioral traits. It mentions the readOnly mode constraint but fails to specify whether the termination is a soft cancel or hard kill, required permissions (e.g., superuser), side effects (e.g., connection closure), or behavior for invalid PIDs. This is insufficient for a destructive operation.

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 very concise with only two sentences, no redundant information, and front-loads the core action 'Terminate an active query by PID'. Every sentence serves a purpose.

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 destructive nature and no output schema, the description should explain return values (success/failure), error conditions (e.g., PID not found), and prerequisites (e.g., need to identify the query first). The readOnly mode note is helpful but incomplete. The agent lacks sufficient context to use it safely.

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%, so baseline is 3. The description adds no additional semantics beyond what the schema provides for 'pid' and 'connectionId' (both clearly documented in schema). It does not clarify how to obtain the PID or validate connectionId values.

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 terminates an active query by PID, using a specific verb (terminate) and resource (active query by PID). It distinguishes itself from sibling tools like pg_active_queries (which lists queries) and mysql_kill_query (MySQL equivalent).

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 provides no explicit guidance on when to use this tool versus alternatives, such as when a query is stuck or needs cancellation. It does not mention prerequisites (e.g., needing the PID from pg_active_queries) or when not to use it, leaving the agent to infer context.

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