Create Salesforce MCP Server

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 useful context beyond annotations by specifying the created files (package.json, tsconfig.json, src/index.ts, etc.) and the subsequent build commands. No contradiction.

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?

Five sentences, each adding a distinct piece of information: purpose, file list, SDK context, input requirement, and post-generation steps. It is front-loaded with the purpose and avoids unnecessary fluff, though slightly longer than the minimal ideal.

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?

The description gives sufficient context for an agent to invoke the tool and follow up: what it creates, the key input, and next steps. No output schema is expected, and the description covers the tool's behavior adequately. It doesn't mention that no org connection is made, but that's not critical for a scaffolding operation.

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% for all four parameters. The description's mention of outputDirectory as an absolute path only reiterates the schema. It adds no significant new parameter semantics, so baseline 3 applies.

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 'Generates a complete, working MCP server project structure on disk targeting a Salesforce org' with a specific verb and resource. It lists concrete files generated, making it distinct from siblings like sf_create_mcp_tool which likely creates a tool rather than the server scaffold.

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 clear context: instructs the agent to 'Provide an outputDirectory (absolute path)' and gives post-generation steps ('run npm install' then 'npm run build'). It lacks explicit exclusions or alternatives, but the uniqueness of the tool makes the usage obvious.

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