create_scheduled_job

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

The description adds the prerequisite 'requires WRITE_ENABLED=true', which implies a write operation consistent with annotations (readOnlyHint=false). However, it does not disclose other behaviors such as side effects, error conditions, or return format. No contradiction with annotations.

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 efficiently conveys the purpose and a key prerequisite. No unnecessary words or repetition.

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?

With 6 parameters and no output schema, the description provides minimal context beyond the prerequisite. It does not explain the response upon creation or any follow-up actions. The schema is detailed, but for a creation tool, agents might benefit from knowing what to expect (e.g., job ID).

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 100%, so the schema already describes all parameters. The description does not add any additional meaning beyond the schema, such as parameter constraints or relationships. Baseline score is appropriate.

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 'create' and the resource 'scheduled script execution job', with an additional prerequisite condition (WRITE_ENABLED=true). It distinguishes itself from other 'create_*' siblings by specifying the scheduled script execution nature.

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 only mentions a prerequisite condition (WRITE_ENABLED=true) but does not provide context on when to use this tool versus alternatives or when not to use it. No comparison with sibling tools or scenarios.

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