ftp_list_transactions

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

No annotations are provided, so the description carries full burden. It does not explicitly state that the operation is read-only, nor does it define 'recent' or disclose any side effects. The word 'Expose' implies read access, but this is not guaranteed.

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 a single sentence that efficiently conveys purpose and use case. It is front-loaded but could be slightly more precise (e.g., specifying 'read-only').

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?

With no output schema and no annotations, the description is missing details about return structure, data freshness, and whether the operation is safe. It covers purpose and context but not enough for a complete understanding.

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?

The input schema is empty (0 parameters, 100% coverage), so description cannot add parameter semantics. Baseline of 3 is appropriate.

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 uses the verb 'Expose' and clearly identifies the resource as 'recent mutations currently stored in the system's SnapshotManager'. It distinguishes from siblings like ftp_rollback (action vs. list) and ftp_list_deployments (different resource).

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 states 'Essential for planning rollbacks', which provides a clear context for when to use this tool. However, it does not explicitly exclude alternatives or state when not to use, but the sibling tool ftp_rollback suggests this is a preparatory step.

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