salesforce_search

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

No annotations are present, so the description carries full responsibility for behavioral disclosure. It only states 'Run a SOSL full-text search', implying a read operation, but fails to mention important traits like return format, pagination, error handling, or authentication requirements beyond the schema. For a tool with no annotations, this is insufficient.

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 a single concise sentence with no waste. It lacks structure (e.g., bullet points or sections), but it is appropriately sized for a simple tool. Slightly better structure could improve scannability.

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 search tool with no output schema and two parameters (one required), the description is minimal. It does not specify what the output contains (e.g., records, fields), how results are ordered, or limitations. Given sibling tools like 'salesforce_query' which likely have more detail, this description feels incomplete.

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 'sosl' and '_sfAuth' are documented in the schema). The description adds no additional meaning beyond the schema, so the baseline of 3 is appropriate.

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 'Run a SOSL full-text search across objects' clearly states the verb (Run) and resource (SOSL full-text search across objects). It distinguishes from sibling tools like 'salesforce_query' (SOQL) and 'salesforce_get_record' (single record retrieval).

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 phrase 'SOSL full-text search' implies it is for cross-object full-text search, suggesting it should be used when querying multiple objects or fields with text matching, versus 'salesforce_query' which is for SOQL. However, no explicit when-to-use, when-not-to-use, or alternatives are provided.

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