get_brief

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

Annotations already indicate readOnlyHint=true (safe, non-destructive). Description adds that the brief is curated, omits retracted decisions, and is not a raw context dump – giving the agent clear expectations about the content. No contradictions with 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?

Extremely concise, front-loaded with the core purpose. Every sentence serves a purpose: what it does, when to call it, what it contains, and clarifying it's curated. No fluff.

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 presence of an output schema (not shown but indicated), the description doesn't need to detail return format. It covers all relevant aspects: project focus, content summary, and exclusion of raw dumps. Sibling tools are distinct, so no missing comparisons.

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% (baseline 3). Description adds semantics for token_budget: 'lowest-priority items drop first', explaining behavior beyond the schema's 'Max tokens'. Also notes project defaults to current project, though schema already says default null. Slight value over baseline.

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 it 'Load the prioritised hand-off brief for a project' and explains what the brief contains (goal, next step, key decisions, etc.). Distinguishes from sibling tools, none of which serve this specific session-start function.

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 the 'START of a session, before doing anything else'. Provides clear when-to-use context and implicitly advises against using it mid-session.

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