git_clone

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

Despite no annotations, the description discloses that the tool performs a write operation recorded in the audit log, and explains the conditional apply and gateway_id disambiguation. This goes beyond a simple 'clone' statement. Missing details like error handling or idempotency, but core behavioral traits are covered.

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 highly concise: one clear purpose sentence, concise conditional explanation, audit note, and bullet-style Args. Every sentence adds value with no redundancy. Structure is logical and front-loaded.

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 no output schema or annotations, the description should cover return values, error scenarios, and prerequisites. It explains the workflow but does not mention what the tool returns (e.g., success message, cloned directory path) or what happens on failure (e.g., invalid URL, permission issues). Adequate for basic use but incomplete for robust agent selection.

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?

With 0% schema description coverage, the description's Args section adds essential meaning: repo_url is 'HTTPS or SSH', branch defaults to main, cluster_name triggers apply, gateway_id disambiguates. This compensates well for the schema's lack of descriptions, though some constraints (e.g., exact URL format) are not specified.

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 starts with a clear verb+resource statement: 'Clone a git repository onto the VibOps gateway.' It further explains the conditional behavior with cluster_name, distinguishing the tool's dual purpose (clone only vs. clone+apply). This purpose is distinct from sibling tools, which are mostly unrelated operations.

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 provides explicit context for when to include cluster_name (apply manifests) and when to include gateway_id (disambiguation for multi-gateway deployments). However, it does not explicitly state when to use this tool over alternatives, though no direct alternative exists among siblings. The conditional guidance is clear.

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