search_records

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('Search for') but lacks details on permissions needed, rate limits, pagination behavior, error handling, or what the search encompasses (e.g., fields searched). This is inadequate for a tool with potential complexity in Salesforce environments.

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, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 complexity of searching across multiple Salesforce objects, no annotations, and no output schema, the description is insufficient. It doesn't explain return values, search scope limitations, or behavioral traits like authentication needs, leaving significant gaps for an AI agent to use the tool effectively.

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%, with clear parameter descriptions in the schema. The description adds no additional meaning about parameters beyond implying a cross-object search scope, which is already suggested by the schema's 'object_types' array. This meets the baseline for high schema coverage.

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 verb ('Search for') and resource ('records across multiple Salesforce objects'), providing a specific purpose. However, it doesn't differentiate from sibling tools like 'soql_query' or 'get_record', which might offer alternative search approaches, preventing a perfect score.

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 provides no guidance on when to use this tool versus alternatives. With siblings like 'soql_query' (likely for structured queries) and 'get_record' (likely for single-record retrieval), there's no indication of appropriate contexts, exclusions, or prerequisites for this multi-object search tool.

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