push_local

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It does reveal the sequence of operations (stage, commit, push), which adds value beyond the name. However, it omits important behavioral traits such as whether the push can overwrite remote changes, requires authentication, or what happens on conflicts. This lack of consequence disclosure is a significant gap for a mutation tool.

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 exceptionally concise: one sentence explaining the core actions plus one sentence for differentiation. Every word earns its place, and the key information is front-loaded. No filler or redundant phrasing.

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 and no annotations, the description should explain expected return values and side effects. It does not mention what the tool returns after a successful push (e.g., version ID, success message) or what happens if remote changes exist. It also assumes familiarity with a 'registered workspace' without referencing setup prerequisites. This leaves the agent under-informed for a mutation tool.

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. The description adds minimal meaning beyond the schema; it reiterates that paths are optional ('Stage (all, or the given paths)') and implies projectName is the target, but the schema already holds those details. This matches the baseline for high coverage.

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 tool's function: 'Stage (all, or the given paths), commit, and push the registered workspace back to Overleaf.' It uses specific verbs (stage, commit, push) and identifies the resource (workspace to Overleaf). It also distinguishes itself from siblings by explicitly claiming to be 'the only tool that pushes workspace edits,' which separates it from pull_local and other sync operations.

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 clear context: use this tool to push workspace edits to Overleaf. It explicitly states it is the only tool that does so, which implies alternatives like pull_local or sync_projects are not for pushing. However, it does not explicitly mention when not to use it (e.g., when you only need to stage or commit locally without pushing) or prerequisites like having a registered workspace.

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