push_files

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

Without annotations, the brief description fails to disclose critical behaviors: whether it creates a new commit, overwrites existing files, or requires an existing branch. Missing details on idempotency, error handling, and authorization needs.

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 concise sentence with no redundancy. However, given the tool's complexity, it may be too terse, sacrificing clarity for brevity.

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?

With no output schema, no annotations, and 4 undocumented parameters, the description is insufficient. It lacks return value details, behavioral constraints, and parameter guidance, leaving significant gaps 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?

Schema coverage is 0%; the description does not explain parameters beyond the implied 'files' and 'commit_message'. project_id and branch are left completely undocumented, forcing agents to guess or rely on parameter names alone.

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 (push), target (GitLab project), object (multiple files), and modality (single commit), distinguishing it from sibling tools like create_or_update_file (single file).

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 batched file operations but offers no explicit guidance on when to use push_files vs alternatives like create_or_update_file for single files or commit-based workflows. No prerequisites or constraints are mentioned.

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