refresh_file

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

Annotations declare readOnlyHint=false and destructiveHint=false, so the agent knows this is a non-destructive mutation. The description adds useful behavioral context (incremental, avoids walking the workspace, <50ms), which is real value beyond annotations, but it omits auth requirements and what happens when the file is missing or unchanged.

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?

A single tight sentence with no waste, and the operation and its performance scope are front-loaded. Acceptable, though the parenthetical '(re-)chunk' is slightly awkward.

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 an output schema present, return values need not be explained. However, the 0%-covered parameter and the absence of usage/exclusion guidance leave the description only minimally adequate for a mutation 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 description coverage is 0% and the sole parameter rel_path is undocumented in both schema and description. The description does not clarify that the path is relative or how it is resolved, so it fails to compensate for the coverage gap.

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?

States a specific verb (re-chunk and re-index) applied to a specific resource (a single file), and the incremental scope distinguishes it from the sibling refresh_index. It does not explicitly name refresh_index as the workspace-wide alternative, so it falls short of a 5.

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 incremental, single-file scope implies when to use it (after editing one file) versus refresh_index, but this is left implicit. There is no explicit when/when-not statement or named alternative.

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