sf_unschedule_apex_job

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It fails to mention that unscheduling is a destructive/mutating action, whether confirmation is needed, what happens to running jobs, or any side effects such as aborting all matches. The existence of parameters like confirm and abortAllMatches hints at significant behavior that is not disclosed.

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 short sentence that is front-loaded with the action verb and is free of fluff. It earns its place by stating the core purpose, but it lacks any structural elements (e.g., separators, examples, or parameter notes) that would help an agent parse more complex behavior. It is concise but minimal to the point of being under-specified.

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 tool with 6 parameters, no annotations, no output schema, and 0% schema description coverage, a one-sentence description is completely inadequate. It does not explain the semantics of confirmation, abortAllMatches, directory, or targetOrg, nor does it warn about consequences of unscheduling jobs. The agent would have no idea how to properly invoke this tool beyond the basic action.

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. It only mentions jobId and jobName, providing minimal meaning for these two parameters, but leaves confirm, directory, targetOrg, and abortAllMatches completely unexplained. The tool has 6 optional parameters with no required fields, which is confusing and not clarified by the 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 clearly states the verb 'Unschedule' and the resource 'scheduled jobs', with a qualifier 'by jobId or jobName' that specifies the identification method. This distinguishes it from sibling tools like sf_schedule_apex_job and sf_execute_batch_job, making the purpose unambiguous.

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 gives no explicit guidance on when to use this tool versus alternatives, nor does it provide exclusion criteria or prerequisites. It mentions jobId or jobName as options but does not explain when to prefer one over the other or when not to use the tool. The inverse relationship with sf_schedule_apex_job is implied but not stated.

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