sf_execute_apex_cursor_query

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

With no annotations, the description carries the full burden. It mentions execution via anonymous Apex, which implies running code in the org, but does not disclose whether the operation is read-only, permission requirements, Apex governor limits, or what the return value contains. This is a significant gap for a tool that executes code.

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 sentence, but it is under-specified for a tool with 16 parameters. While it avoids fluff, it fails to provide essential context, making it more of a one-line summary than a useful tool description.

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 high complexity (16 params, no annotations, no output schema), the description is severely incomplete. It does not explain what a 'cursor query' is, how pagination works, what the execution returns, or any prerequisites. This is not enough to guide correct invocation.

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 input schema has 16 parameters and 0% description coverage. The description provides no meaningful explanation of any parameter (e.g., soqlQuery, objectName, whereClause, pagination controls). This leaves the agent completely in the dark about parameter semantics.

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 states a clear compound action: building Apex cursor query code and executing it via anonymous Apex. It distinguishes from related siblings like sf_build_apex_cursor_query (likely only builds) and sf_execute_anonymous_apex (executes arbitrary code), though it doesn't explicitly mention 'cursor' pagination specifics.

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 explicit when-to-use guidance is provided. The phrase 'in one step' hints at a combined operation but does not explain when to choose this over alternatives like sf_execute_anonymous_apex or sf_query_org_paginated.

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