Create Scheduled Apex Job

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

Annotations already indicate readOnlyHint=false, idempotentHint=false, and destructiveHint=false. The description adds a prerequisite and an example cron expression, but doesn't disclose additional behavioral traits like error handling or what happens on duplicate job names. It doesn't contradict the annotations, but information beyond same is limited.

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 three sentences, with the purpose front-loaded, followed by usage context and a concrete example. Every sentence adds information, making it appropriately sized.

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 simple scheduled-job creation tool with no output schema, the description covers the core purpose, use cases, prerequisite, and an example. It doesn't discuss error conditions or validation, but given the annotations and sibling context, it is sufficiently complete.

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 coverage is 100%, so the baseline is 3. The description adds value by stating 'The Apex class must already exist in the org' for className and providing an example cron expression that clarifies the format. While jobName gets no extra detail, the additional context for the other two params justifies a 4.

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 specific action: 'Schedules an Apex class that implements the Schedulable interface to run on a cron schedule.' It clearly identifies the resource (Apex class) and distinguishes from sibling tools like sf_create_scheduled_flow by focusing on Apex classes.

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 explicitly lists use cases: 'batch processing, nightly data cleanup, report generation, or any periodic automation.' It also provides a prerequisite ('The Apex class must already exist in the org'), giving clear context. However, it doesn't explicitly mention alternatives or when not to use this tool, so it stops short of a 5.

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