Deploy Flow from Raw XML

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

Annotations already declare non-read-only, idempotent, and non-destructive behavior. The description adds valuable context: uses Metadata API zip deploy, auto-defaults start locationX/locationY, and pre-validates three specific schema errors. No contradiction with annotations.

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 multi-sentence but well-structured and front-loaded: action, use case, activation, and validation notes. Every sentence carries meaningful information, though it could be slightly condensed without loss.

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?

There is no output schema, but the description explains prerequisites (complete Flow XML), behavior (deploy and optional activation), and error-prevention validations. It is sufficient for an agent to invoke correctly, especially with sibling status-check tools like sf_check_deploy_status available.

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 baseline is 3. Parameter meanings are fully documented in the schema. The description adds only marginal semantics (e.g., confirming flowXml must be complete), though the pre-validation details are more behavioral than parametric.

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 clear action: 'Deploys a Salesforce Flow directly from raw XML using the Metadata API zip deploy.' It explicitly distinguishes itself from the sibling tool sf_create_flow by targeting complex flows beyond the parameter-based builder.

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?

Provides explicit guidance: 'Use this for complex flows that are too advanced for sf_create_flow's parameter-based builder' and mentions optional activation. This tells the agent exactly when to select this tool over the named alternative.

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