session_primer

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

Description states 'Read', consistent with readOnlyHint annotation. No additional details about error cases (e.g., missing primer) or side effects, but annotations already declare read-only behavior. Minimal added value beyond annotations.

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, front-loads the primary action and purpose. Every word contributes; no filler or repetition. Highly 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 zero-parameter, read-only tool with output schema absent, the description adequately explains purpose and usage timing. Could mention handling of missing primers, but not essential given simplicity.

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?

No parameters exist in the input schema, so the description naturally covers parameter semantics. Per guidelines, 0 parameters yields baseline 4, and the description adds no redundant info.

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?

Clearly states the verb 'Read' and the specific resource 'most recent session handoff primer' with the goal 'to restore context from the previous session'. Differentiates from sibling tools like start_handoff and complete_handoff by specifying its unique role at session start.

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?

Explicitly instructs to 'Call at session start', providing clear timing. While it does not list when not to use or alternatives, the context of session start is sufficiently specific.

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