retrieve_session_context

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states 'retrieve' without explaining wildcard behavior for session_id, default limits, auth requirements, or what 'stored session context' includes. This is a significant gap for a tool with five parameters.

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 a single sentence with no verbosity or fluff, making it appropriately concise and front-loaded. It earns its place by clearly naming the operation, though it lacks detail. It is not under-specified to the point of being a tautology, but it is minimal.

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 tool has five parameters, one required, and no output schema, yet the description provides no context about return values, wildcard behavior, filtering, or how it relates to store_session_context and update_session_context. The description is too sparse to be fully usable in a complex context.

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 100%, as every parameter (key, limit, session_id, context_key, context_type) has a description in the input schema. The description adds no additional parameter semantics beyond what the schema already provides, so the baseline of 3 is appropriate.

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 'Retrieve stored session context' clearly identifies the verb (retrieve) and resource (session context), making the core purpose understandable. However, it does not distinguish this from sibling tools like memory_search, search_semantic, or get_recent_activity, all of which could also retrieve something. It is clear but lacks differentiation.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention any prerequisites, scenarios, or exclusions. Users are left to infer usage from the name alone, which is insufficient given the similar sibling tools.

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