trigger_scheduled_job

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

Annotations show readOnlyHint=false and destructiveHint=false. The description adds that WRITE_ENABLED=true is required, providing behavioral context beyond annotations. It does not detail side effects, but for a simple trigger action this is acceptable.

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 that is front-loaded with the main action and includes the prerequisite. Every word adds value; no waste.

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 the tool's simplicity (one required parameter, no output schema), the description is sufficient. It explains what the tool does and a key requirement. It does not explain return values but that is often assumed for such actions.

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% with one parameter 'sys_id' described as 'Scheduled job sys_id to trigger'. The description does not add additional meaning beyond the schema, but it is consistent and clear.

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 'Immediately execute a scheduled job on-demand', specifying the verb 'execute' and resource 'scheduled job'. It distinguishes from siblings like 'get_scheduled_job' or 'update_scheduled_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 indicates when to use (on-demand) and includes a prerequisite (WRITE_ENABLED=true). It does not explicitly mention alternatives, but context from sibling tools makes the purpose clear.

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