reload_buffer

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the action ('reload from disk') and context ('after editing externally'), but doesn't specify whether this operation is destructive to unsaved changes, what permissions are needed, or what happens on failure. For a mutation tool with zero annotation coverage, this leaves significant behavioral questions unanswered.

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 perfectly concise with two sentences that each serve distinct purposes: the first states the core function, the second provides usage context. There's zero wasted language, and the information is front-loaded with the essential action before the contextual guidance.

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 a single-parameter tool with 100% schema coverage but no annotations and no output schema, the description provides adequate basic context about when to use the tool. However, for a mutation operation that could potentially discard unsaved buffer changes, more behavioral transparency would be beneficial. The description is complete enough for basic understanding but leaves operational risks unspecified.

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 schema description coverage is 100%, with the single parameter 'path' clearly documented in the schema. The description doesn't add any parameter-specific information beyond what the schema provides, such as path format examples or constraints. With complete schema coverage, the baseline score of 3 is appropriate as the description doesn't enhance parameter understanding.

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 a buffer from disk') and resource ('buffer'), making the purpose immediately understandable. It distinguishes from siblings like 'reload_all_buffers' by specifying single-buffer operation, though not explicitly contrasting with 'update_buffer'. The description avoids tautology by explaining what reloading entails.

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 clear context for when to use this tool ('after editing a file externally to refresh the buffer in Neovim'), which is helpful guidance. However, it doesn't explicitly mention when NOT to use it or name alternatives like 'reload_all_buffers' for multiple buffers or 'update_buffer' for different operations. The guidance is practical but not comprehensive about alternatives.

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