salesforce_setup

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

With no annotations provided, the description carries full burden but only states what parameters to configure. It doesn't disclose whether this persists credentials, requires authentication, has side effects, returns confirmation, or handles errors. 'Configure' implies a write/mutation operation but lacks behavioral details.

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?

Extremely concise single sentence with zero waste. Every word contributes directly to the tool's purpose. The structure is front-loaded with the core action and immediately specifies what's being configured.

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?

For a credential configuration tool with no annotations and no output schema, the description is insufficient. It doesn't explain what happens after configuration, whether credentials are validated, what the expected outcome is, or how this interacts with other Salesforce tools. The complexity of credential management warrants more complete guidance.

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 parameters are fully documented in the schema. The description lists the three parameters by name but adds minimal semantic context beyond what's already in the schema descriptions. Baseline 3 is appropriate since the schema does the heavy lifting.

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 action ('Configure') and the resource ('Salesforce credentials') with specific parameters listed. It distinguishes this as a setup/configuration tool rather than data operations like query or create, but doesn't explicitly differentiate from sibling 'salesforce_auth' which might have overlapping functionality.

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?

No guidance on when to use this tool versus alternatives like 'salesforce_auth' or other setup-related tools. The description implies this is for initial credential configuration but doesn't specify prerequisites, timing, or whether this should be used before other Salesforce operations.

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