salesforce_get_contact

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

The description only adds routing and scoping context (JWT, tenant, company scope) but does not disclose operational side effects. This is especially concerning because annotations mark destructiveHint=true and readOnlyHint=false, yet the description offers no warning or explanation for a seemingly read-oriented 'get_contact' action.

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 brief and well-organized with an Args list, front-loading the action name without wasted words. It is concise, but some of the included content is generic rather than informative.

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?

Key context is missing: how to populate `inputs` to identify the contact, when to prefer this over dispatch_domain_agent or the other Salesforce tools, and what the destructiveHint annotation implies. The output schema exists, so return-value documentation is not needed, but the invocation requirements are under-specified.

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?

The schema has 0% description coverage, so the description must compensate. It only explains that `message` is a free-text objective and `inputs` is an optional JSON string, but it does not specify what structured inputs are needed to target a contact (e.g., contact ID, email), leaving agents unable to construct a valid call.

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 it runs the salesforce `get_contact` domain agent action and routes through the dispatcher, but it does not functionally state that it retrieves a contact. It relies on the action name for meaning and does not differentiate from sibling tools like salesforce_get_account or salesforce_search_contacts.

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?

There is no guidance on when to use this tool versus alternatives such as salesforce_search_contacts, salesforce_get_account, or the generic dispatch_domain_agent. Usage must be inferred entirely from the tool name.

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