app-file_revert

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

No annotations are provided, so the description must disclose side effects. It says 'reload from disk' but does not explicitly state that unsaved changes will be lost, which is a critical safety behavior for a revert operation. The statement 'force is always required' hints at a confirmation step but does not describe the destructive nature fully.

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 with no wasted words. It is front-loaded with the purpose and includes the key usage condition iconcisely.

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 no output schema and a single parameter, the description covers the basic action but lacks a warning about discarding unsaved changes. While the tool is simple, the destructive nature of reloading should be highlighted for safety. The description is adequate but minimal.

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 description adds meaning to the single parameter 'force' by stating it is always required, which the schema does not convey (default false). This clarifies that the must be set to true for the tool to function, which is valuable beyond the schema's title and default.

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 action: 'Reload the current file from disk'. This is specific and distinguishes it from save/open operations among siblings. The verb 'reload' and resource 'file from disk' are unambiguous.

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 a usage condition: 'force is always required', indicating that the tool will only work when force is set to true. It does not explicitly state when to use vs alternatives, but the purpose is clear enough that the context implies discarding unsaved changes.

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