load_context_files

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

With no annotations, the description carries the full burden. It discloses that files are loaded into context and tagged with hashes for change detection, but does not explicitly state whether the operation is read-only or if there are any side effects beyond modifying the active context.

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, consisting of two clear sentences, and front-loads the core action followed by useful detail. No extraneous information is included.

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?

The description explains the tool's behavior and its relationship to reload_active_context_file, but does not mention what the tool returns or whether there is any output. Since there is no output schema, this gap is minor but present.

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?

Both parameters are fully described: 'files' explains the relative path format with an example, and 'project_path' lists the three accepted forms (absolute path, owner/repo, or URL). This exceeds the schema descriptions.

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 loads specific .context/-relative files into the active context, and explains the tagging mechanism with path and SHA-512 hash. This makes the purpose 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 explicit guidance to only pass files actually needed and to avoid loading the whole tree, but does not directly contrast with sibling tools like search_context_index or reload_active_context_file.

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