repo_analyze_repository

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

No annotations exist, so the description carries the full burden. It discloses key behaviors: scans all files, performs AST parsing, detects patterns, and generates an AI summary. This goes beyond a minimal description and gives the agent a good sense of what the tool does. It does not mention performance impact or file modification, but the read-only nature of 'analyze' is implied.

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 two sentences, front-loaded with the primary purpose and followed by a concise process summary. Every word earns its place; no redundant or vague language.

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?

The tool has one simple parameter and no output schema. The description explains its purpose and process, and it explicitly mentions the AI summary as the output. While it does not detail the exact output format, the description is sufficient for an agent to understand what the tool does and what to expect. Slight room for more detail on return structure, but overall complete.

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 input schema has 100% coverage for the single parameter 'path' with a clear description ('Absolute path to the repository root directory'). The tool description does not add additional parameter semantics beyond the schema, but given full schema coverage, the baseline of 3 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 a specific verb+resource: 'Analyze a local repository to understand its structure, framework, dependencies, and architecture.' It further details the process (scans all files, AST parsing, detects patterns, generates an AI summary), which distinguishes it from sibling tools like repo_scan_files (just scans) or repo_summarize_repository (just summarizes). This is a comprehensive analysis tool with a clear scope.

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 implies usage when a deep understanding of a repository is needed, but it does not explicitly state when to use this tool versus alternatives like repo_explain_architecture or repo_scan_files. There is no mention of exclusions or when to choose a different sibling. The context is clear but not explicit.

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