List custom objects

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

With no annotations provided, the description carries the behavioral disclosure burden. It does add useful context by revealing that this runs 'a Tooling API SOQL query on CustomObject' and returns Tooling API Ids. It does not explicitly confirm read-only behavior, ordering, or output shape beyond the Ids, but 'List' and 'query' imply a non-mutating operation.

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 two sentences with no filler. The primary purpose is front-loaded, and the downstream usage hint ('Use the returned Id with sf_delete_custom_object') is a valuable, compact addition.

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?

For a simple list tool with no output schema and no annotations, the description provides the core information: what is listed, how it is queried, and what the returned Ids are for. It does not detail every return field, but the stated purpose of obtaining Tooling API Ids is sufficient for the intended use.

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?

Schema description coverage is 100%: both 'limit' and 'search' already have meaningful descriptions in the input schema. The tool description adds no additional parameter-level detail, so the baseline of 3 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 states a specific action ('List'), a clear resource ('custom objects in the org'), and a key output detail ('Tooling API Ids'). It also distinguishes this from general object listing by specifying custom objects and the Tooling API query mechanism.

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 implies a usage context by saying 'Use the returned Id with sf_delete_custom_object,' which helps the agent understand one downstream purpose. However, it does not explicitly state when to prefer this tool over siblings like sf_list_objects or sf_soql_query, nor does it mention exclusions.

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