pushRepo

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

With no annotations, the description carries full burden but only states 'Pushes changes'. It does not disclose behavioral traits such as authentication needs (though schema has optional user/password), conflict handling, or that it might modify remote repositories. The mutation aspect is implied but not elaborated.

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 extremely concise (one sentence) and front-loaded. However, it may be too minimal for the complexity of the tool, lacking essential details. Still, no wasted words.

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, no annotations, 5 parameters (including two nested objects), and a mutation operation, the description is severely incomplete. It does not explain return values, error behavior, or required prerequisites like authentication. The tool's complexity demands more context.

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 schema already documents each parameter. However, the description adds no additional meaning or context beyond the schema, such as clarifying what the 'repo' or 'staging' objects should contain or how 'connection' is used. Baseline 3 is appropriate.

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 'Pushes changes to a Git repository' clearly states the action (pushes) and the resource (changes to a Git repository). It distinguishes from sibling tools like 'stageRepo' (staging) and 'gitPullRepo' (pulling), but lacks specificity about whether it pushes to a remote or local repository.

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 is provided on when to use this tool versus alternatives like 'stageRepo' or 'gitPullRepo'. There are no prerequisites, exclusions, or context for usage decisions.

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