create_job

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

Annotations only provide a title, so the description carries full burden. It states this creates a new job but lacks behavioral details like required permissions, whether it's idempotent, what happens on failure, or if it triggers immediate execution. The mention of 'minimal set of fields' hints at constraints but is vague.

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, efficient sentence that front-loads the core purpose without unnecessary words. It's appropriately sized for a tool with good schema coverage, making every word count.

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 minimal annotations, the description is incomplete for a creation tool. It covers the basic action but lacks details on return values, error handling, or behavioral traits, leaving gaps that could hinder agent usage despite good schema coverage.

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 fully documents parameters. The description adds no additional meaning beyond implying 'minimal fields' might relate to required parameters, but it doesn't clarify which fields are minimal or provide usage context beyond the schema.

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 action ('Create') and resource ('Agent Job'), specifying it's a new job with minimal fields. It distinguishes from siblings like 'cancel_job' or 'get_job' by being the creation tool, though it doesn't explicitly contrast with 'list_jobs' or 'get_jobs_stats'.

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?

No guidance on when to use this tool versus alternatives is provided. It doesn't mention prerequisites, dependencies, or contrast with sibling tools like 'list_jobs' for viewing existing jobs or 'cancel_job' for stopping them, leaving the agent to infer usage context.

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