Git worktree list

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

The description repeats 'Read-only' which is already declared by readOnlyHint=true in annotations, adding no new behavioral information. It does not disclose any other traits like output size, path interpretation, or whether it operates on the current repository only. Since annotations cover safety, the description adds minimal value beyond that.

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 very short and front-loaded with the verb and object, which is concise. However, it is too sparse, omitting critical parameter guidance. It earns a middle score because conciseness is good but the content is insufficient for a complete tool spec.

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?

Although an output schema exists (so return format is covered), the description is incomplete because it fails to explain the sole parameter. Given the tool is simple, the missing parameter semantics are a critical gap. The description does not provide enough context for correct invocation.

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?

Schema coverage is 0%, so the description must explain the 'path' parameter. It does not. There is no mention of what path refers to (e.g., repository path, worktree path) or any format hints. The agent has no additional information beyond the parameter name.

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 uses a specific verb ('List') and resource ('worktrees of a repository'), making the action unambiguous. It clearly distinguishes from sibling tools like git_worktree_create and git_worktree_remove, which are mutations. No ambiguity about what the tool does.

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?

No guidance on when to use this tool versus alternatives. It does not mention conditions such as 'to inspect worktree state before modifying' or exclusions (e.g., 'not for creating/removing'). The context is implied by the name, but no explicit usage rules are provided.

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