Register Git repository

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

Annotations declare readOnlyHint=true, but the description says 'Register' which implies a write operation to create a registry entry. This is a direct contradiction. The description adds no meaningful behavioral context beyond the conflicting annotation.

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 sentence with no redundant words. While it is minimal, it is appropriately sized for the tool's apparent simplicity, though it could benefit from a bit more detail.

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 annotations and an output schema, but the description does not explain the registration semantics, what happens if the path is invalid, or why readOnlyHint is present. This inconsistency and missing context make the description incomplete for an agent.

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 schema has one parameter 'path' with no description, and schema description coverage is 0%. The description does not explain what 'path' should be (e.g., absolute/relative, worktree directory). The agent has no semantic guidance for this parameter.

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 action ('Register'), the resource ('Git worktree'), and the output ('return its repositoryId'). This distinguishes it from sibling tools, which are all read/list/compare 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 implies usage for registering a worktree but does not explicitly say when to use this tool versus alternatives. There is no mention of alternative tools or exclusions, leaving the usage context vague.

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