session_briefing

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

Beyond annotations (readOnly, idempotent), the description details what the tool assembles (active tasks, recent lessons, git activity, project health) and how it provides discoverability parity with other tools. No contradictions with annotations; adds valuable behavioral context.

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 concise paragraphs: first sentence states primary use, second paragraph explains dual behavior (with/without project). Every sentence adds value, no fluff, and the critical info is front-loaded.

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 low complexity (1 param, no required, output schema exists), the description fully covers what the tool does, what it returns in both cases, and how it fits with sibling tools. It is complete for an agent to decide when and how to invoke 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% with a clear description for the 'project' parameter. The description adds extra meaning by clarifying the slug is a directory under 10_projects/, that empty lists projects, and explicitly stating there is no 'days' argument – fixed briefing window. This reduces ambiguity beyond the schema.

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 the tool loads project context at session start. It distinguishes from siblings by being a consolidated briefing that replaces multiple manual calls, and notes behavior without a project (returns project list) for discoverability parity with vault_health and worker_status.

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 says 'Call at the start of every new session' and explains what happens with and without a project. It also contrasts with alternatives by stating it replaces 3-4 manual calls, giving clear usage context.

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