aap_create_job_template

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

The description discloses the return format ('JSON with created template id, name, and launch URL') and provides an example with become/check flags. However, it does not disclose idempotency, failure behavior, or other side effects beyond creation.

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 concise and well-structured with purpose, example, args, and returns sections. It is front-loaded with the main verb and resource.

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?

For a create tool with many parameters, the description gives an example and return info but lacks guidance on when to use it vs update/copy and does not mention required relationships like existing project and inventory. The schema provides field-level detail, so it is minimally adequate.

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 description only points to 'See field descriptions' without summarizing or explaining parameters. With 0% schema description coverage in the description, it fails to compensate for parameter understanding beyond what the schema already provides.

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 'Create a new AAP job template' with a specific verb and resource. It distinguishes the tool from sibling tools like update, delete, list, and launch.

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 through an example but does not explicitly state when to use this tool versus alternatives, nor does it mention prerequisites like existing projects or inventories.

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