Initialize project context

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

With no annotations provided, the description fully carries the transparency burden. It discloses several important behaviors: auto-registration, project detection via git remote/.agent-memory.json/path, returning a briefing and protocol, conditional user prompt about unfinished work, and silent background memory bookkeeping. It does not explicitly state whether the tool modifies files or if any destructive actions occur, but 'auto-registers' implies a state change, which is adequately transparent for an initialization tool.

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 four sentences long and information-dense, with no wasted words. It is slightly longer than necessary but each sentence carries essential guidance (when to call, what it does, when to ask the user, how to handle memory commands). The critical 'call first' instruction is front-loaded, which is well-structured.

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?

Given the tool's moderate complexity, no output schema, and no annotations, the description covers the essential context: behavior, return value (briefing + protocol), and usage pattern. It does not describe error cases or the exact structure of the briefing, but those are not strictly required for the agent to invoke the tool correctly. The description is sufficient for an agent to know when and how to call it.

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 schema descriptions for focus, agentId, and workspacePath are already clear. The tool description itself does not add additional parameter-level meaning beyond what the schema provides. According to the rubric, this lands at the baseline score of 3.

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 states a specific verb ('initialize'), the resource ('project context'), and the exact behavior: detect the current project, auto-register it, and return a briefing plus an AGENT PROTOCOL. It clearly distinguishes itself from sibling tools like get_project_context (which retrieves existing context) and save_memory (which stores specific memories) by positioning itself as the session-start entry point.

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 description is explicit about when to use it: 'Call this FIRST, automatically, at the start of EVERY chat/session — without the user asking.' It also provides a clear exclusion: memory bookkeeping (save_memory, create_handoff, finish_session) must happen silently and never be left to the user. This leaves no ambiguity about the tool's role versus its siblings.

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