terminate_backend

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

In absence of annotations, description fully discloses write operation, high risk, no undo, audit trail capture, refusal of own PID, and dry_run behavior. No contradiction with annotations (none provided).

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?

Well-structured with tags [WRITE][risk=high], clear summary, then args. Slightly verbose but efficient for the complexity. Every sentence adds value.

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?

Covers input semantics and constraints well, but does not describe return value/output. Given no output schema and moderate complexity, this is a minor gap.

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?

With 0% schema coverage, description adds valuable meaning for all three parameters: pid (source from list_activity), dry_run (preview vs. execute), and target (config-driven, optional).

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?

Description explicitly states 'Terminate a backend (pg_terminate_backend)' and distinguishes from sibling tools like cancel_query by noting high risk, no inverse, and audit trail capture.

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?

Provides clear when-to-use (dry_run for preview) and behavior under refusal, but does not explicitly compare to alternative tool cancel_query or state when not to use terminate.

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