drop_slot

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

No annotations provided, so description carries full burden. It discloses irreversibility, WAL release, subscriber impact, and dry-run guard, giving comprehensive behavioral insight beyond schema.

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?

Four sentences, front-loading key points (exact name, irreversibility). Every sentence adds essential information with no redundancy.

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 behavior, guard condition, and outcome for subscribers. Lacks explicit mention of prerequisites (e.g., slot exists) or error handling, but is otherwise complete for a simple drop 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 coverage is 0%, but description adds meaning: slot_name must be exact name, allow_writes controls dry-run. Could further detail slot_name origins or allow_writes format, but current info is useful.

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 clearly states the tool drops a replication slot by exact name and emphasizes irreversibility. It distinguishes from siblings like list_replication_slots and advance_slot by specifying the destructive exact-name operation.

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 context: irreversible, dry-run unless allow_writes=true and env var set. Does not explicitly mention when not to use or suggest alternatives, but siblings imply other tools for different operations.

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