List Salesforce Sandboxes

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

Annotations indicate readOnlyHint, idempotentHint, openWorldHint, and non-destructive. The description adds behavioral context beyond these: it explains the output includes both SandboxInfo and optionally SandboxProcess lists, and emphasizes the production org requirement. No contradictions with annotations.

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 well-structured with clear sections (Description, Args, Returns, Note). It is concise, no filler sentences, and all information is front-loaded. Every sentence adds value to the agent's understanding.

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 tool's complexity (list with optional progress tracking) and lack of output schema, the description completely covers input parameters, return types, and an important usage constraint (production org). No gaps for an AI agent to select and invoke correctly.

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 0%, but the description explains both parameters in the Args section: include_in_progress controls the inclusion of SandboxProcess records (default true), and response_format defaults to markdown. This adds necessary meaning that the schema lacks. The return structure is also described.

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 lists all sandboxes via Tooling API SandboxInfo, distinguishing it from sibling tools like salesforce_metadata_query (for SandboxProcess) and salesforce_create_sandbox (for creation). It specifies the verb 'list', the resource 'sandboxes', and the scope 'under the production org'.

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 explicit guidance: it lists sandboxes and includes in-progress creations, and suggests using salesforce_metadata_query for SandboxProcess status. The note 'must be run against the PRODUCTION org' is a crucial usage constraint. However, it does not explicitly state when not to use this tool versus alternatives like salesforce_query.

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