context_pack

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

No annotations provided, so description carries full burden. It discloses token-bounded output, max_tokens default, and scoping via file/repo_path. Could mention side-effect free or idempotency, but sufficient for non-destructive tool.

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 concise sentences, no fluff. Core purpose front-loaded, followed by usage guidelines and parameter clarifications. Excellent structure.

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 7 parameters and no output schema, description covers key aspects: purpose, when to use, token limit, and two parameters. Missing details on some parameters but overall adequate for basic usage. Could benefit from a brief example.

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 0%, but description explains two parameters (file, repo_path) with usage context. Other parameters (query, max_tokens, include_*) are not elaborated, though names are self-explanatory. Adds some value but incomplete.

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 'budget-packs code + episodic context into a token-bounded block' for prompt injection. It distinguishes from raw file reads and provides specific usage directives (call before reading files, avoid for short files).

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 says 'Call this BEFORE reading any source file' and 'Do NOT call for known short files (< 50 lines) — use Read directly instead.' Provides clear when-to-use and when-not-to-use with alternative.

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