salesforce_search_all

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

The description goes beyond the readOnlyHint annotation by explaining wildcard usage (* and ?), per-object independent WHERE/ORDER BY/LIMIT clauses, and supported WITH clause types. It provides concrete examples of advanced search configurations, adding useful behavioral context without contradicting annotations.

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 well-structured with two examples and bullet-point notes, making it easy to scan. It is lengthy but each section earns its place given the tool's complexity, though a brief output format note could improve efficiency.

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 thoroughly explains input construction and supported features, covering all parameters with real examples. However, since there is no output schema, a description of the response structure would enhance completeness; this omission prevents a 5.

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?

Input schema descriptions cover 100% of parameters, so baseline is 3. The description adds value by showing how parameters combine in real examples, such as using searchIn, withClauses, and object-level properties together, which the schema alone does not convey clearly.

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 'Search across multiple Salesforce objects using SOSL (Salesforce Object Search Language)', which identifies the specific verb, resource, and method. It distinguishes from sibling tools like salesforce_query_records by specifying SOSL and 'across multiple objects', making its purpose unambiguous.

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 when to use this tool through its focus on SOSL cross-object search, providing clear context for selecting it over SOQL-based siblings. However, it does not explicitly state when not to use it or name alternative tools, so it falls short of a 5.

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