salesforce_list_custom_objects

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

The description adds useful context beyond annotations by disclosing that execution routes through the platform's domain-agent dispatcher under JWT, tenant, and company scope. However, it does not elaborate on the destructiveHint=true annotation or what side effects the action may have, though it does not contradict it.

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 short, front-loaded, and uses a clear Args section with no filler. The first sentence is somewhat redundant with the tool name, but the overall structure is efficient.

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?

Annotations and an output schema cover safety and return shape, and the description covers invocation and scoping. The main missing pieces are a real statement of the action's purpose and when to use it; a name-only hint is weak for a catalog with many Salesforce list tools.

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 description coverage, the description compensates by defining `message` as a free-text objective and `inputs` as an optional JSON string of structured inputs. This is sufficient at a generic level, but it does not explain what keys or values the structured inputs should contain for listing custom objects.

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 only says 'Run the salesforce domain agent action `list_custom_objects`,' which effectively restates the tool's name without explaining what listing custom objects does or returns. The domain-agent routing sentence adds context but no functional purpose, leaving the agent to infer everything from the tool name.

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 choose this tool over sibling tools such as salesforce_list_accounts, salesforce_list_opportunities, or dispatch_domain_agent. The description mentions routing and scoping but provides no exclusions, prerequisites, or alternative-selection criteria.

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