get_agent_bootstrap

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

No annotations are provided, so the description must carry full burden for behavioral traits. It mentions the payload size (~300 tokens) but does not state whether the call is read-only, requires authentication, or any side effects. For a bootstrap tool, it lacks disclosure of performance or error behavior.

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 concise, with a clear opening sentence, bullet-pointed return values, and an explicit usage instruction. Every sentence adds value, and the structure makes it easy for an agent to parse.

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 annotations or output schema, the description adequately covers the tool's purpose, return values, and context of use. It explains what each returned field means and when to use it, making it complete for an agent to decide and invoke correctly.

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 described as 'optional absolute path to the target repository'. With 0% schema description coverage, the description adds complete meaning. The description of the parameter is clear and sufficient for an agent to understand its purpose.

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 that this tool is a single-call session bootstrap replacing a 4-call sequence, and explicitly lists the resources it returns (repo, architecture, hot_symbols, etc.). It distinguishes from sibling tools like get_session_brief, get_last_context, etc.

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 says 'call this ONCE at session start instead of the 4 individual calls' and advises to use individual tools only when full detail is needed. This provides clear when-to-use and when-not-to-use guidance.

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