sf_schedule_apex_job

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

With no annotations provided, the description carries full responsibility for disclosing side effects. It does not state that scheduling is a mutating operation, whether confirmation is required (despite the 'confirm' parameter in the schema), or what happens on success. The description is completely devoid of behavioral context.

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 with no redundant words, making it efficient to parse. However, it is almost too brief to be useful, sacrificing substance for brevity. It earns a 4 because it contains no waste, but the conciseness is not appropriately balanced with completeness.

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?

This tool has six parameters, no output schema, and no annotations, yet the description only states the basic purpose. It does not explain the meaning of required parameters, the confirmation behavior, target org selection, or return values. This is completely inadequate for an agent to safely and correctly invoke the tool.

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 description indirectly references 'cron expression' and 'Schedulable Apex class,' which loosely map to cronExpression and className. However, it fails to explain jobName, confirm, directory, targetOrg, or the expected format of the cron expression. With 0% schema description coverage, the description only partially compensates for two of six parameters.

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 action ('Schedule a Schedulable Apex class') and the method ('using a cron expression'). This is a specific verb+resource combination that distinguishes it from sibling tools like sf_unschedule_apex_job or sf_execute_batch_job.

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 no guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., the class must implement Schedulable), exclusions, or that unscheduling uses a different tool. There is no context to help the agent choose correctly among related scheduling tools.

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