reload_active_context_file

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

With no annotations provided, the description carries full responsibility. It transparently discloses the comparison behavior and the three distinct outcomes: fresh content for changed files, 'no change' for unchanged, and 'not found' for deleted. This gives the agent a complete picture of the tool's behavior without hidden side effects.

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 concise, using two sentences to convey the core action and expected outcomes. There is no redundant or extraneous information, and the structure is logical, starting with the action and then describing the return behavior.

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?

Although there is no output schema, the description explicitly explains what the tool returns for each possible scenario (changed, unchanged, deleted). With only two parameters and a clear return contract, the description is sufficiently complete for correct usage.

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 already provides 100% coverage of both parameters, including descriptions for 'files' (list of path and known_sha512) and 'project_path'. The tool description does not add significant extra meaning beyond the schema, so the 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 clearly states the tool's function: checking whether files in active context have changed on disk by comparing SHA-512 hashes. It also distinguishes itself from the sibling tool load_context_files, which presumably loads files, by focusing on change detection and returning updated content only for modified files.

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 implies usage when you need to detect changes to already-loaded files, and it clarifies that unchanged files yield a 'no change' message and deleted files yield 'not found'. It does not explicitly mention alternatives or when not to use it, but the purpose is clear enough for the agent to decide.

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