Version Control

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

Annotations declare readOnlyHint: true and destructiveHint: false, but the description includes many mutating actions (create_issue, update_issue, merge_pull, etc.), creating a direct contradiction. Beyond that, the description does not disclose any behavioral traits such as authentication needs, rate limits, or side effects.

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 overly long due to an exhaustive list of actions, which could be condensed or grouped. It starts with a clear purpose statement, but the bulk is a repetitive list that adds little value. It is not concise.

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 tool with 24 parameters and many sub-actions, the description is severely lacking. It does not explain what each action does, when to use them, or what the return values are. The annotations contradict, and no output schema exists. The description is inadequate for effective tool 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?

Schema description coverage is 100%, so the baseline is 3. The description does not add any additional meaning to parameters beyond what the schema already provides; it merely lists action names. The schema's parameter descriptions are minimal but present.

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 states 'Git version control and remote repo operations' and lists specific actions, clearly indicating the tool's broad scope. It distinguishes from sibling tools by focusing on VCS operations, though it doesn't explicitly differentiate from potentially overlapping tools like 'execute_operation'.

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 no guidance on when to use this tool versus alternatives. It simply lists actions without any context on prerequisites, limitations, or when to prefer other tools. No 'when not to use' or alternative tool references are provided.

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