push_files

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose batch capability and single-commit semantics, but it omits important mutating behaviors such as whether existing files are overwritten, whether the branch must already exist, and what permissions are required. For a write operation this is a significant transparency gap.

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 focused sentence with no filler. The most important qualifiers ('multiple files' and 'single commit') are front-loaded, making it easy for an agent to parse quickly.

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 description covers the core operation and the schema fully documents parameters, but there are no annotations and no output schema. It omits when-to-use guidance and important behavioral details like overwrite semantics and branch prerequisites. This is adequate for a simple push operation but leaves clear gaps for an autonomous 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?

Schema description coverage is 100%, so the input schema already documents all five parameters clearly. The description adds no per-parameter detail beyond what the schema provides, which matches the baseline of 3.

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 a specific verb ('Push'), a clear resource ('GitLab repository'), and a useful qualifier ('multiple files... in a single commit'). This makes the tool's purpose immediately distinguishable from siblings such as create_merge_request or create_branch.

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 gives no guidance on when to choose this tool over alternatives, such as create_merge_request or create_branch. It does not mention any exclusions, prerequisites, or conditions that would make a different sibling tool more appropriate.

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