analyze_repository

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

The description provides no behavioral details such as whether the analysis is read-only, what permissions are needed, whether it has side effects, or what output is returned. With no annotations, the agent lacks critical information about the tool's runtime behavior, leaving a significant transparency gap.

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 a single, front-loaded sentence that efficiently conveys the tool's purpose with no unnecessary words or redundancy. It is optimally concise and well-structured.

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 a nested config object with multiple toggles and no output schema, yet the description is minimal. It does not explain how to use the config parameter, what the tool returns, or any behavioral constraints. This is insufficient for an agent to invoke the tool correctly in varied scenarios.

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?

Although the schema has 100% coverage, the description adds no explanation of the 'config' parameter or its options. The description lists security, performance, and quality, but the schema also includes 'enableDocumentation', which is not mentioned, creating a mismatch. The description adds little beyond the schema's property names and types.

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 analyzes a git repository for security, performance, and quality issues. It uses a specific verb and resource, and is unambiguous. The only sibling tool is 'ping', which serves a different purpose, so there is no confusion.

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 context by stating what the tool does, but it does not explicitly say when to use it or provide alternatives. Since the only sibling is 'ping', the intended use is reasonably obvious, yet there is no formal guidance on when to choose this tool over others.

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