salesforce_deploy_apex_class

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is covered. The description adds useful auth and routing context by noting it dispatches under JWT, tenant, and company scope. It does not contradict the annotations and provides behavioral context beyond them.

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 short, uses an Args block, and front-loads the action name. It is easy to scan and contains minimal filler. Some space is given to routing context that could have been replaced with tool-specific deployment details, but the structure itself is clean.

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?

For a deployment action with no schema-level parameter descriptions, the description should explain prerequisites, how to specify the Apex class, and what the dispatcher will do. It provides none of that and instead acts as a generic wrapper. The presence of an output schema covers return values, but the input and usage gaps remain significant.

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%, so the description must compensate, but it only says message is a free-text objective and inputs is an optional JSON string of structured inputs. This is circular and does not specify what structured inputs are expected for deploying an Apex class, such as class name, body, or API version. An agent cannot construct a correct inputs payload from this description.

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 says it runs the Salesforce domain-agent action `deploy_apex_class`, which names the resource only through the action identifier rather than explicitly stating what deployment does. It does not distinguish itself from sibling tools like salesforce_deploy_flow or salesforce_deploy_validation_rule. The verb 'run' plus the action name is understandable but not a direct statement of the tool's effect.

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 information is provided about when to use this tool versus alternatives such as salesforce_deploy_flow, salesforce_deploy_permission_set, or other Salesforce CRUD tools. There are no exclusions, conditions, or scenarios mentioned. The description only gives routing mechanics, not selection guidance.

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