load_session

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

No annotations provided, so description carries full burden. It discloses that it only returns context passing trust threshold, never injects low-confidence or stale sessions, and returns summary and block. However, it does not specify behavior when no session exists or error conditions.

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?

Two sentences with no redundancy. First sentence states action and expected output; second adds critical constraint. Fully front-loaded and efficient.

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?

For a simple tool with one optional parameter and no output schema, the description covers purpose, return values, and trust threshold. It is complete enough for an agent to use correctly, though it omits edge cases like missing session.

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 coverage is 100% and the description adds minimal new insight beyond the schema. It reinforces the threshold's role but does not elaborate on format or usage semantics.

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?

Description clearly states 'Load' action on 'last verified session context from CognOS Session Memory' and specifies output: summary and inject-ready block. It distinguishes from sibling 'save_session' by verb and scope, and adds constraint about trust threshold.

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?

Description implies use for retrieving a verified session context but does not explicitly state when not to use or alternative tools. It mentions trust threshold but lacks exclusionary guidance such as 'use save_session to create a session'.

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