get_context_briefing

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

Although no annotations are provided, the description discloses the tool is read-only (retrieval), token-capped, and focuses on key context items. It does not mention authentication needs or rate limits, but the behavior is sufficiently clear for a safe operation.

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?

Three efficient sentences: purpose, usage recommendation, and content overview. Every sentence adds unique value with no redundancy.

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 description covers purpose, usage, and content types. Given the tool has 3 optional parameters and no output schema, the lack of explicit return format (e.g., JSON vs text) is a minor gap, but overall adequate for a simple retrieval tool.

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% but the description adds value by explaining scope as 'module/directory scope to focus the briefing' and repo as 'uses default if omitted'. For max_tokens, it restates the schema's default but adds context about being a budget.

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 clearly states the tool returns 'a ranked, token-capped briefing of the most important context for this codebase'. This specific verb+resource combination distinguishes it from sibling tools like get_recent_decisions or get_open_problems.

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 explicitly recommends use 'at the START of a session to efficiently prime your understanding'. It does not specify when not to use or name alternatives, but the context and sibling list imply appropriate scenarios.

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