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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safe-read profile is covered. The description adds useful context that the pack was "previously saved" and originates from "another AI conversation," but says nothing about what loading actually does to state (e.g., whether it injects context, overwrites anything, or how the pack is selected among matches).

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 well-formed sentence that front-loads the verb and resource. Every word earns its place; there is no filler or redundancy.

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?

An output schema exists and annotations cover the safety profile, so return values and side-effect risk need not be re-explained. What is missing is guidance on the id-vs-query resolution path and the role of maxChars, which is the main thing an agent needs to call this correctly.

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 description says nothing about parameters. Crucially, the tool accepts two different lookup modes (id vs. query) and the description never explains the id/query duality or that either is optional, leaving the agent to infer the selection strategy from the schema alone. With only 67% schema coverage, the description does not compensate for the 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 ("Load") and resource ("previously saved CortexPlus context pack") with the intended outcome ("resume work started in another AI conversation"). It distinguishes itself implicitly from read/list siblings like context_packs, but never explicitly names an alternative tool, 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 phrase "to resume work started in another AI conversation" implies the usage context (re-entering a prior session), which is more than nothing. However, it never states when to prefer this over recall, context_packs, or connect, and gives no prerequisites or exclusion conditions.

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