push_file

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true. The description adds real value beyond that: it names exactly what is destroyed ('a file at the same path is replaced'), discloses the user confirmation gate in the MCP client, and warns that project content is collaborator-authored data. Return format and failure modes for a bad local path are still unstated.

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?

Four sentences, purpose front-loaded, each adding a distinct fact: path inference, replacement behavior, confirmation gate, and safety notice. The prompt-injection sentence is boilerplate but relevant for a tool that ingests collaborator content; nothing is redundant.

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 mutation tool with full schema coverage and rich annotations, the description covers the essentials an agent needs: what it does, what it overwrites, that user confirmation precedes the write, and how project content should be treated. No output schema exists, but the write semantics are sufficiently explained.

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 all three parameters, making 3 the baseline. The description restates the remote-path inference rule but refers to 'the file_path argument' when the actual parameter is 'local_path', a naming mismatch that slightly muddies rather than clarifies. No additional syntax or format guidance is added.

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 and resource: 'Upload a local file to an Overleaf project.' This clearly separates it from siblings like download_file and pull_project, which move data the other direction. The follow-on sentence about remote path inference further pins down the operation.

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 upload direction implies when to use it versus download_file/pull_project, and the note about user confirmation sets expectations. However, no alternative is named and no explicit when-not or prerequisite conditions are given.

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