salesforce_list_objects

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

With no annotations provided, the description carries the behavioral burden. It discloses that results are filtered by the current user's access, includes both standard and custom objects, and lists the returned capability flags such as queryable, createable, updateable, and deletable. It does not mention pagination or API limits, but for a zero-parameter listing tool the key behaviors are covered.

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 main purpose is front-loaded in the first sentence, and the follow-up sentences add meaningful detail about scope and return fields. There is minor redundancy between 'List all available SObjects' and 'Returns a list of all objects,' but the overall structure is clear and focused.

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 tool's simplicity, zero parameters, and presence of an output schema, the description is largely complete. It explains what the output contains and the access-based filtering. It does not discuss large-org truncation or pagination, but this is a plausibly acceptable omission for a listing tool.

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 tool has zero parameters, so the input schema is already fully complete. The description does not need to explain parameter meaning. The baseline of 4 applies.

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 tool's action and resource: 'List all available SObjects in the Salesforce org.' It is specific and conveys the scope (all objects accessible to the current user), but it does not explicitly differentiate itself from sibling tools like salesforce_describe_object or salesforce_get_object_fields.

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 gives clear context for when to use the tool: when you need an enumeration of available standard and custom objects accessible to the current user. It does not mention exclusions or explicitly compare with alternatives, but the 'list all' framing makes the primary use case unambiguous.

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