context_load

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

No annotations exist, so the description carries the burden, and it does a solid job: it describes rendered output groups, the first-line identity/index-freshness warning, and the full disabled behavior. It does not fully clarify normal side effects such as whether an outbox flush occurs when enabled.

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 organized into purpose, when-to-use, output format, and disabled behavior. Every sentence earns its place and the most important information is front-loaded.

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 covers purpose, usage, output structure, and disabled behavior well, but it leaves all four parameters unexplained and does not describe normal-operation side effects or error behavior. For a tool with no annotations and no output schema, those gaps matter.

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 description adds no meaning for cwd, outbox_dir, token_budget, or audit_log_path. The name hints are not enough, and token_budget in particular needs behavioral context that is absent.

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 opens with a specific verb and resource: 'Load previously saved context for the current project and render it.' It also names the output grouping, making its role distinct from sibling tools like context_save, context_archive, and the memory_* family.

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?

Provides explicit guidance: use at the start of work on a project, especially on an unfamiliar machine or tool. It also warns when the tool is disabled, though it does not contrast itself with memory_get or context_save alternatives.

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