run_sosl_search

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It merely states execution without mentioning read-only nature, side effects, permissions, rate limits, or return format. The description adds minimal behavioral context.

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 very short—two sentences. The 'Args:' line is slightly redundant but does not waste space. It is front-loaded with the main action. However, important details are omitted in favor of brevity.

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 complexity (executing a SOSL query) and absence of annotations or output schema, the description is far too minimal. It lacks prerequisites, behavior details, error handling, and result format guidance, making it incomplete for reliable agent 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?

The single parameter 'search' has 0% schema description coverage. The description compensates slightly by providing an example ('FIND {John Smith} IN ALL FIELDS'), which adds meaning beyond the bare schema. However, it does not explain syntax rules, escaping, or limitations.

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 'Executes a SOSL search against Salesforce,' with a specific verb (executes) and resource (SOSL search). However, it does not differentiate from the sibling tool run_soql_query, which is a closely related query type.

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 provided on when to use this tool versus alternatives like run_soql_query or other record retrieval tools. The description lacks context for appropriate usage scenarios.

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