advance_slot

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

With no annotations, the description discloses irreversibility, discarding changes before to_lsn, dry-run behavior, and the environmental prerequisite. This provides sufficient transparency for safe use.

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 convey the purpose, irreversibility, parameter requirements, and dry-run behavior without redundant information. Every sentence earns its place.

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 three parameters and presence of an output schema, the description covers all essential behavioral and usage aspects: slot advancement, irreversibility, LSN specification, and write safeguards. No gaps remain.

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%, but the description adds full meaning: slot_name and to_lsn are identified as 'exact slot name and target LSN', and allow_writes is explained with dry-run logic. All parameters are covered.

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 states 'Advance a replication slot to an EXPLICIT LSN (irreversible)' with a clear verb and resource. It distinguishes from siblings like 'drop_slot' and 'peek_changes' by specifying the slot advancement action and explicit LSN requirement.

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?

It explains that the exact slot name and target LSN are required, and dry-run is the default unless allow_writes=true and the server variable is set. While it doesn't explicitly mention when not to use or alternatives, the context is clear for a focused tool.

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