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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, and the description is consistent with that by saying the output is returned after checking ('checked statically with RPScripts Lab before it is returned') rather than describing server-side mutation. It adds genuine behavioral context beyond annotations: which framework install entries are emitted (shared jobs entry or ESX SQL), that a README is included, and that a static validation gate runs before return. Minor gap: it doesn't confirm whether any files are written to disk, which would fully resolve the 'create' vs readOnlyHint tension.

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 opening clause is well front-loaded (verb, resource, frameworks) and the preset/spec sentence earns its place. However, the middle is a single sprawling enumeration of ~20 feature components that reads as a feature dump, and the trailing template list duplicates the preset enum verbatim, so not every token pays for itself.

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?

There is no output schema, so the description carries the return-value burden, and it does so reasonably: it describes the generated resource contents, the framework install entries, and the README, and it flags that results pass static validation first. It could say more about error/validation-failure behavior or the exact return shape, but an agent has enough to call it correctly.

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 already 80% and the schema documents the name/label/preset/spec overrides. The description reinforces the preset-plus-spec composition and notes the spec replaces the template, but it repeats the template list that is already an enum and adds no format detail for the free-form nested spec object beyond pointing at rpcrate.job.json. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

States a specific verb and resource: 'Generates a complete job resource with the RPScripts Jobs Creator for QBCore, Qbox or ESX', followed by the concrete artifacts produced (job definition, grades, duty, stash, garage, install entries, README). This is clearly distinguishable from generation siblings like generate_script or generate_fxmanifest because the resource type and framework scope are named up front.

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 explains the two invocation strategies explicitly: 'Start from a template (preset) and/or pass a full spec', and gives an iterative workflow ('generate a preset, edit that file, pass it here'). It stops short of the 5 level because it never states when NOT to use this tool or names the sibling to use instead (e.g. validate_resource for an existing resource).

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