salesforce_query_all

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It usefully explains that the query includes deleted and archived records, which is the main behavioral distinction. However, it does not explicitly confirm read-only semantics, mention rate limits or pagination, or describe how results behave beyond the return phrase. Given the absence of annotations, a bit more behavioral context would be valuable.

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 compact, front-loaded with the essential behavior, and avoids redundant filler. The Args/Returns structure makes the content scannable, and every sentence earns its place. The only slight repetition ('including deleted and archived records' twice) is minor and does not hurt clarity.

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?

This is a simple one-parameter tool and an output schema exists, so the description does not need to explain return types in depth. It provides the core behavior, the equivalent underlying call, and the parameter meaning. It could add explicit read-only confirmation or pagination behavior, but those are not critical for a basic SOQL query tool with this simplicity level.

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 coverage is 0% and the only parameter is a bare string, so the description's 'soql: SOQL query string' adds real semantic meaning by identifying what the string should contain. It does not provide syntax examples or formatting guidance, but for a single self-explanatory SOQL parameter this is adequate, though not rich.

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 opens with a specific action and resource: 'Execute a SOQL query including deleted and archived records.' This clearly differentiates the tool from the sibling salesforce_query while still identifying the core query behavior. An agent can immediately know what this tool does and how it differs from related query tools.

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 explicitly states that this tool is equivalent to salesforce_query with include_deleted=True, which names the relevant alternative and the key condition for choosing this variant. It stops short of saying 'use this when you need deleted/archived records' in explicit terms, but the meaning is clear and actionable.

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