ensure_repo

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

With no annotations, the description explains the core behavior (clone/reuse), the result (path and status), and a side effect (resets 5-minute idle timer). It covers the essential behavioral traits a caller needs, though it omits failure handling and auth details.

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 sentences with zero redundancy. The main action is first, followed by usage guidance and return/timer info. Every sentence provides distinct value.

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?

For a simple setup tool with a high-coverage schema, the description covers the purpose, usage order, return value, and side effect. No output schema exists, so the stated return of path and status suffices.

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?

Both parameters are fully described in the schema (repoUrl and branch), giving 100% coverage. The description adds operational context but no additional parameter semantics, so a baseline 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 the tool's function with a specific verb and resource: 'Clone a Git repo to a temp directory (or reuse existing clone).' It also distinguishes itself from siblings by noting it should be called first, making its role unique.

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 instructs 'Call this first before search_repo, read_file, or list_directory,' providing direct usage ordering and naming specific sibling alternatives. This is a clear when-to-use statement.

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