sf_deploy_metadata_validate

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

No annotations are provided, so the description carries the full burden. It discloses the key non-destructive behavior ('without committing changes'), but does not explain what validation entails—whether tests run, how conflicts are handled, or what output to expect. This is more than a tautology but lacks operational detail.

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 a single, clear, front-loaded sentence with no filler words. It is concise and readable, though it is arguably too brief for a tool with 9 parameters and no additional documentation.

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 tool's complexity (9 parameters, no output schema, no annotations), the description is insufficient. It establishes the core purpose but omits prerequisites, relationship to sf_deploy_metadata, expected outputs, and any guidance on parameter usage, making it incomplete for safe autonomous invocation.

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 gives no information about any of the 9 parameters. Parameters like manifest, sourceDir, tests, targetOrg, and ignoreConflicts are entirely unexplained, leaving the agent without semantic guidance beyond their names.

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 uses a specific verb ('Validate') and clear resource ('Salesforce metadata deployment'), and adds the critical qualifier 'without committing changes.' This clearly distinguishes it from the sibling tool sf_deploy_metadata, which performs an actual deployment.

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 phrase 'without committing changes' implies this is a dry-run validation, useful before an actual deployment. However, it does not explicitly name sf_deploy_metadata as the alternative for committing changes, nor does it state when validation should be preferred.

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