boot_report

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

States 'Read-only — does not modify any stored data,' and describes the read operations in detail (reads identity document, scans memory database, finds transcript, detects gaps, calculates score). With no annotations provided, the description fully discloses behavioral traits.

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 relatively long but well-structured. It starts with the purpose, then lists the steps, and ends with guidance. Every sentence adds value, though brevity could be improved slightly without losing content.

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 complexity (multiple data sources, gap detection, score calculation, and capture handling), the description covers every aspect. It even provides follow-up actions for PreCompact captures. No output schema exists, but the description adequately describes the output elements.

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?

Input schema has 100% description coverage, so baseline is 3. The description adds context beyond the schema by explaining how each parameter is used in the tool's workflow (e.g., 'Reads the identity document from disk' for identity_path). This adds meaningful value, raising the score to 4.

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's purpose: 'Generate a session orientation report.' It specifies the verb 'generate' and the resource 'orientation report,' and distinguishes from sibling tools by noting it is read-only and should be called first thing each session.

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 this first thing every session to establish context before doing any work.' Also provides guidance on when to use sibling tools: 'If PreCompact captures exist, call list_captures and read_capture...' This provides clear usage context and alternatives.

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