salesforce_list_accounts

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

Annotations declare readOnlyHint=false and destructiveHint=true, yet the description does not warn about side effects or explain why a 'list' action could be destructive. It adds context about JWT/tenant/company scope but fails to disclose the behavioral implications of routing through the domain-agent dispatcher.

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-structured: a one-line purpose, a brief routing note, and an Args list. It contains no filler, though it could use the available space to add more substantive guidance.

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 leaves major gaps: no when-to-use guidance versus sibling Salesforce tools, no explanation of the dispatcher's behavior, no input format guidance, and no reconciliation of the destructiveHint annotation. An output schema exists, but the invocation context is still insufficiently 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 description adds basic meaning beyond the bare schema: message is a 'free-text objective' and inputs is an 'optional JSON string of structured inputs.' However, schema description coverage is 0%, so this thin labeling only partially compensates; there is no detail about expected input structure, examples, or how the message should be phrased.

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 the exact verb and resource: 'Run the salesforce domain agent action `list_accounts`.' This clearly identifies the tool's purpose and distinguishes it from generic Salesforce actions, though it does not explicitly contrast it with siblings like salesforce_get_account or salesforce_list_opportunities.

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 is given about when to use this tool versus alternatives such as salesforce_get_account, salesforce_soql_query, or salesforce_passthrough. The description mentions that it routes through the domain-agent dispatcher but never states the intended use case or conditions for selection.

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