Schedule Background Job

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

Annotations already flag destructiveHint=true, and the description adds specific behavioral context: immediate=true immediately starts an ABAP program, and jobCount/jobName can be used for SM37 monitoring. This goes beyond the structured annotation by explaining the side-effect timing and safe-use boundary, though it does not detail error or authorization behavior.

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 front-loaded with the action and warning, followed by a compact arg list, return shape, and two examples. The only rough edge is the bare 'response_format.' line in the Args list, which adds some noise but no significant bulk.

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 five parameters and no output schema, the description covers the operation, side effects, safety warning, return JSON shape, and monitoring instructions. The schema fills in types, defaults, and constraints. It does not explain the immediate=false path in the description, but the schema's default documentation covers that, so nothing critical is missing.

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?

All five parameters have schema descriptions (100% coverage), so the baseline is 3. The description adds value by explaining the role of job_name (visible in SM37), clarifying variant as optional, and giving concrete natural-language-to-parameter mappings in the examples, exceeding the schema's basic descriptions.

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 first sentence, 'Create and schedule an ABAP background job via JOB_OPEN + JOB_SUBMIT + JOB_CLOSE,' names a specific verb, resource, and underlying SAP function modules. This clearly distinguishes it from siblings like sap_run_report (foreground execution) and sap_run_console.

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 an explicit when-not restriction: 'Only use in development/sandbox or when you are certain of the effect.' It also includes natural-language examples like 'Schedule ZMONTHLY_CLOSE now' to illustrate typical user inputs. It does not explicitly name alternative sibling tools, but the background-job semantics plus safety warning make the appropriate context clear.

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