List a project's git worktrees

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

Description aligns with readOnlyHint=true annotation, adds behavioral context: worktreeDir is outside the repo by default, and the ticket id derivation. No contradictions. Adds value beyond annotations.

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?

Four concise sentences, front-loaded with the core purpose. Each sentence adds value: operation, returned fields, extra context, and read-only note. No redundancy or waste.

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 the simple nature of the tool (one param, no output schema), the description completely covers what the agent needs: what it lists, the fields returned, and a pointer to a related caveat. Adequate for a read-only list operation.

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 sole parameter 'project' is described as the project identifier for the code repo. With 0% schema description coverage, the description provides meaningful semantics beyond the type definition.

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 lists git worktrees for a project's code repo, specifying the exact fields returned (path, branch, HEAD, isMain, ticket id) and the worktreeDir. This distinguishes it from siblings like create_worktree or cleanup_worktree.

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 mentions 'Read-only' and references a caveat on create_worktree, but does not explicitly state when to use this tool versus alternatives or when not to use it. Usage is implied but not made explicit.

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