df_push

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

With no annotations provided, the description successfully discloses a key behavioral trait: 'Requiere confirm: true para ejecutar. Sin confirm devuelve preview.' This tells the agent that the tool is preview-only by default and only mutates the remote when confirm=true. It does not discuss potential failure modes or remote state effects beyond that.

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 only two sentences and front-loads the primary action. Every word contributes meaning; no filler or redundant schema repetition.

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?

Given the simple one-parameter tool and no output schema, the description covers purpose, parameter behavior, and safety confirmation. It lacks explicit mention of remote mutation side effects, but the 'push' action and confirm gate largely compensate.

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?

Beyond the schema's 'true para ejecutar el push', the description clarifies that omitting confirm yields a preview, which is not stated in the schema. This fully defines the parameter's behavior and default.

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: 'Hacer push de la rama actual al remote' (push the current branch to the remote). It uses a specific verb and resource, and the action is distinct from sibling tools like df_pull.

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 usage through the action 'push current branch to remote' and explains the confirm requirement, but it does not explicitly state when to prefer this tool over alternatives or when not to use it. No sibling differentiation is mentioned.

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