sf_execute_anonymous_apex

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

The description only states the action of executing anonymous Apex and does not disclose potential side effects, required permissions, or whether it can modify data. With no annotations provided, the description carries the full burden of behavioral transparency and fails to address any of these aspects.

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 concise at one sentence, but it is under-specified for the complexity of the tool. It lacks necessary detail, making it insufficiently informative despite being brief.

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 that this is an arbitrary code execution tool with no output schema and no annotations, the description is far from complete. It does not mention return behavior, error handling, or usage context, leaving the agent without critical information.

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 schema lists four parameters (confirm, apexCode, directory, targetOrg) with no descriptions, and the tool description does not explain any of them. The description mentions the target org but doesn't clarify the meaning of confirm or directory, so it fails to compensate for the 0% schema description coverage.

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 ('Execute') with a specific resource ('anonymous Apex') and mentions the target org, clearly distinguishing it from sibling tools like sf_execute_named_query and sf_query_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?

There is no guidance on when to use this tool versus alternatives such as sf_execute_named_query or sf_schedule_apex_job. The description simply states the action without any contextual usage advice.

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