get_agent_bootstrap

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

With no annotations, the description carries the transparency burden. It discloses the combined nature of the payload, mentions that framing may be empty if tracking is off, and explains the merged timeline. It doesn't explicitly state it's read-only, but the content implies it. A bit more detail on side effects or costs would elevate it to 5.

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 well-structured with a clear first sentence, a bulleted return list, and a usage note. It is longer than the minimum but every part contributes. The reference to 'data/memory/timeline.py::merge()' is slightly over-specified for a typical agent, but the overall formatting is efficient.

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 no output schema, the description thoroughly explains the return shape, including types and examples for each field. It also covers the parameter, alternatives, and usage context. The description is complete for an agent to decide and invoke the tool without further ambiguity.

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?

The only parameter, repo_path, is explained as 'optional absolute path to the target repository.' This adds meaning beyond the schema's anyOf/null/default. It doesn't specify default behavior, but the optionality is clear. For a single parameter, this is adequate.

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: a single-call session bootstrap for AI agents. It explicitly names the four calls it replaces (get_session_brief, get_last_context, get_user_profile, get_error_patterns), making it distinct from siblings.

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?

Provides explicit usage instructions: 'call this ONCE at session start instead of the 4 individual calls' and 'Use individual tools only when you need the full detail each provides.' This clearly delineates when to use this tool vs alternatives.

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