put_file

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

The description adds idempotency as a behavioral trait, but given no annotations, it does not cover authorization, rate limits, or side effects beyond the mutation.

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 sentences with no wasted words, efficiently conveying the core purpose and a key behavioral detail.

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 a complete schema and an output schema present, the description adequately covers the tool's purpose and a critical behavioral nuance, though slightly more usage context could benefit 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 100% (baseline 3), and the description adds value by clarifying idempotency tied to the sha parameter and the create vs. update behavior.

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 ('Create or update a file') and the API source ('via the Contents API'), distinguishing it from sibling read tools like get_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?

It mentions idempotency with correct sha, which implies when to use for updates versus creates, but lacks explicit guidance on when to prefer this tool over others (e.g., not retrieving sha from get_file first).

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