salesforce_query

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

With no annotations provided, the description carries full burden but lacks critical behavioral details. It doesn't disclose whether this is read-only (implied by 'query' but not stated), authentication requirements, rate limits, error handling, or what happens with malformed queries. The description adds minimal behavioral context beyond the basic 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 appropriately concise with two sentences that efficiently convey core functionality. The first sentence states the purpose, and the second adds useful context about supported features. No wasted words, though it could be slightly more front-loaded with critical behavioral information.

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 query tool with no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., query results format), error conditions, authentication needs, or limitations. Given the complexity of Salesforce queries and lack of structured fields, more contextual information is needed for effective 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%, so the schema already fully documents the single 'query' parameter. The description adds marginal value by mentioning SOQL features (SELECT, WHERE, etc.) and implying broad object support, but doesn't provide additional syntax or format details beyond what's in the schema description. Baseline 3 is appropriate when schema does the heavy lifting.

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 tool's purpose: 'Execute SOQL queries against any Salesforce object' with specific verb ('Execute') and resource ('SOQL queries against any Salesforce object'). It distinguishes from obvious siblings like create/delete/update by focusing on querying, though it doesn't explicitly differentiate from salesforce_time_machine_query.

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 usage context by mentioning 'Supports SELECT, WHERE, ORDER BY, LIMIT, and other SOQL features,' suggesting this is for querying data. However, it doesn't provide explicit guidance on when to use this vs. alternatives like salesforce_time_machine_query or salesforce_describe, nor does it mention prerequisites like authentication.

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