Load session context by retrieving current goals and the 20 most recently active notes, so you can orient yourself at the start of every session.
Load session context: current goals + top-20 most recently active notes. Call this at the start of every session to orient yourself.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description carries full behavioral burden. It discloses the payload shape, goals + top-20 recently active notes, which is useful. It does not state whether the call is idempotent or side-effect free, so a small gap remains.
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 zero waste, and the payload summary is front-loaded ahead of the call-to-action. Nothing to trim.
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, so return values need not be explained. The description covers purpose and timing for a zero-arg orientation tool. A note on freshness or cost would make it complete.
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?
Zero parameters means the baseline is 4. The description correctly implies no arguments are needed, matching the empty schema. No compensating detail is required.
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 and resource: load session context comprising current goals plus the 20 most recently active notes. This is more precise than a tautology, but value would rise with explicit routing against siblings like get_decisions or read_note.
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?
Explicit when-to-use with a specific timing rule: 'Call this at the start of every session to orient yourself.' This is a direct, unambiguous instruction that no sibling tool provides.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.