repo_overview

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

No annotations provided, so description carries full burden. It lists the returned data in detail: project name, counts, package manager, config files, entry points, test setup, frameworks, and per-package size map. It implies a read-only, one-call operation. Could mention potential computational cost, but overall transparent.

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?

Concise and well-structured: front-loaded with the key instruction 'run this FIRST', then a clear bullet list of return values. Every sentence is necessary and no waste.

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 purpose (summarizing entire repo) and the presence of an output schema, the description fully covers usage context, return values, and exclusions. Nothing critical is missing.

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 tool has zero parameters, so baseline is 4. The description adds no parameter info beyond what schema already provides (nothing to add), which is appropriate.

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: 'Summarize the entire repository in one call — run this FIRST on an unfamiliar codebase.' It specifies the action (summarize) and resource (repository), and distinguishes from siblings by advising against using for specific symbols/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 when to use: 'run this FIRST on an unfamiliar codebase.' Provides clear when-not guidance: 'Do NOT use for finding a specific symbol or file — use find_symbol or get_file_outline for that.' This directly addresses alternatives.

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