push_binary_files

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

With no annotations, the description carries the full load; it does disclose meaningful behavior: commit semantics via the Git Data API, a 20-file cap, a 50 MB total size cap, and allowlist/denylist enforcement. It omits atomicity (all-or-nothing vs partial failure), whether this creates a new commit or appends to a branch, auth requirements, and error behavior when a path is denied.

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?

Two short sentences, front-loaded with the core action and its limits; nothing is padded. The second sentence is efficient but leans on an undefined external reference, which costs a little clarity for its 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?

For a 5-parameter write tool with zero schema descriptions, no annotations, and no output schema, the description is too thin — it should at minimum clarify branch/message defaults and what the call returns (commit SHA or similar) after success.

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 0% across 5 parameters, so the description must compensate and largely doesn't: it adds meaning only for the files array (binary content, ≤20 entries, 50 MB total), while owner, repo, branch (and its default), message, and the path/content_base64 fields are unexplained. An agent cannot tell from this text whether branch is required or what message defaults to.

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?

States a specific verb+resource (push binary files) plus the batch constraint (up to 20 in a single commit via the Git Data API), which implicitly separates it from the singular sibling push_binary_file. It never names that sibling explicitly, so the differentiation is inferable rather than stated.

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 when-to-use or when-not-to-use guidance; the agent must infer from 'up to 20' that this is the batch variant of push_binary_file. 'Same allowlist, denylist and size limits' is a cross-reference to another tool's documentation without naming it, so the guidance is not self-contained.

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