salesforce_create_contact

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

The description adds useful context about routing through the platform's domain-agent dispatcher under JWT, tenant, and company scope. It does not describe the effect of creating a contact or error behavior, but annotations already convey destructive/read-only hints, and no contradiction exists.

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 compact and well-organized: action, routing context, then args. Every sentence provides distinct information, and the action name is front-loaded.

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 low parameter count, output schema, and annotations, the description covers the core invocation and scoping. However, it omits the actual domain behavior and any guidance on how to express contact creation through `message` or `inputs`, making it less complete for correct selection and 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?

With 0% schema coverage, the description provides the only parameter semantics: `message` is a free-text objective and `inputs` is an optional JSON string. This is helpful but still generic; it does not specify what structured fields an agent should place in `inputs` for a contact.

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 names the exact action (`create_contact`) and states that it runs through the Salesforce domain-agent dispatcher, giving a clear verb and resource. It does not explicitly say 'creates a Salesforce Contact record,' and it relies on the tool name to differentiate from siblings like `salesforce_create_opportunity`.

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 description does not say when to use this tool versus alternatives such as `salesforce_update_contact`, `salesforce_search_contacts`, or `salesforce_passthrough`. It provides routing context but no selection criteria, exclusions, or alternatives.

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