salesforce_query_more

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

No annotations are provided, so the description carries the full burden. 'Retrieve' conveys a read-only action, which is useful, but it does not disclose what happens if the URL is invalid or whether any side effects occur. The description is adequate for a simple pagination fetch but leaves some behavioral assumptions unstated.

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, clear sentence of nine words. It is front-loaded with the action and resource, with zero fluff. Every word earns its place.

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?

The tool is simple and has an output schema, so return values are covered. However, the description does not connect to its sibling 'salesforce_query' or explain where next_records_url originates. Given the moderate complexity, the description is adequate but lacks the contextual linkage that would make it truly complete.

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?

With 0% schema description coverage, the description does not explain either parameter. 'next_records_url' is somewhat self-explanatory, but the description fails to mention that it should come from the previous query response. The optional 'org' parameter is entirely unaddressed. The description adds minimal value beyond the schema.

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 uses a specific verb 'Retrieve' and clearly identifies the resource as 'the next page of a paginated SOQL query'. This distinguishes it from sibling tools like 'salesforce_query' which performs the initial query. The purpose is immediately obvious.

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 'next page' implies this tool is used after an initial paginated query, but it does not explicitly state that it should be used when a previous query returns a nextRecordsUrl, nor does it point to salesforce_query as the origin. The usage context is clear in general terms but lacks specific guidance on when to invoke this over alternatives.

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