Create job

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

Annotations already indicate non-read-only and open-world behavior. The description adds the HTTP method POST and mentions 'one-off job', but does not disclose potential async execution, return format, or other behavioral traits beyond annotations. Minimal added value.

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 short with two sentences but repeats 'Create job' from the title. The link and API reference are useful, but the opening phrase is redundant, reducing conciseness.

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 no output schema and low parameter documentation, the description is incomplete. It lacks details on return values, prerequisites, or conditions for creating a job, leaving the agent with insufficient information for effective use.

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?

The input schema has 3 parameters with only serviceId described. The description does not mention any parameters or their semantics, failing to compensate for the low schema coverage (33%). No additional meaning provided.

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', the resource 'job', and specifies it's a 'one-off job using the provided service'. It includes a link to documentation and the API endpoint, distinguishing it from sibling tools like render_cancel_job or render_list_jobs.

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 implies usage for creating one-off jobs but provides no explicit when-to-use or when-not-to-use guidance compared to alternatives. The link offers further details but the description itself lacks scenario context or exclusions.

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