sync_push

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does note that the user must refresh the browser tab to see changes, which is useful, but it omits potential overwrites, permissions, failure behavior, and effect on connection references. This is too thin for a mutating operation without annotation safety hints.

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 very concise, front-loaded, and contains no filler. 'Push local flow live' states the core action first, and the refresh note is additional useful behavior. It is not bloated, though it is so brief that it borders on underspecification.

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 there are no annotations, no output schema, and a small but non-trivial optional parameter, the description is not complete enough. It fails to explain the connectionReferences parameter and lacks any routing guidance among several closely related sibling tools such as sync_pull and validate_flow. An agent could call it with low confidence about when it is appropriate.

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% and the description does not mention 'connectionReferences' at all. The single parameter is an object with additionalProperties and no semantic explanation, so the agent gets no help understanding what values to provide or whether/how it affects the push.

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 states a specific action and resource: 'Push local flow live.' It clearly conveys that this publishes the local flow to a live environment. However, it does not explicitly distinguish itself from sibling tools like sync_pull beyond the directional 'push' implication.

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?

There is no guidance on when to use this tool versus alternatives like sync_pull, validate_flow, or update_flow. The description implies 'use when you have a local flow to make live,' but it does not state prerequisites, exclusions, or when-not to use it.

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