tex_generate

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

Annotations show readOnlyHint: false (not read-only) and no destructive/idempotent hints, so the description carries the burden. The description does disclose the key behavioral trait: it writes to a free folder rather than to addons ('kein Addon-Schreiben'), which is non-destructive behavior worth noting. However, annotations contradict in nuance - readOnlyHint:false suggests mutation, but the 'kein Addon-Schreiben' implies it doesn't modify project state. Given no annotations cover write behavior, the description provides modest transparency but lacks detail on what happens on repeated runs.

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?

Two sentences, compact and informative. Each sentence earns its place - one states the deliverable and scope, the second provides the pipeline context and purpose. No filler or redundancy. Slightly under-specified on params but structurally efficient.

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 tool with 0% schema coverage, no output schema, and no annotation support for behavior, the description is minimal. It captures the main purpose (generate maps + contact sheet to a free folder) and intended use (experiments/inspection). However, given 4 params are entirely undocumented, and the tool is a pipeline with potential for significant behavior, the description feels incomplete for guiding an agent through correct invocation. The reference to tex_material being 'the same pipeline' helps but assumes agent familiarity.

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 0%, and the description provides NO parameter-level information. The schema itself only lists param names (source, preset, out_dir, overrides) with generic titles and no descriptions or enums. The description mentions 'Gleiche Pipeline wie tex_material' which implies presets/sources work like that sibling tool, but doesn't explain what values these parameters accept, formats, or relationships. For a 4-param tool with zero schema coverage, the description should compensate significantly but doesn't.

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 it generates Maps + a contact sheet into a free folder (not addon-writing). The verb 'erzeugen' (generate) plus the specific deliverable (maps + contact sheet) is specific. It references the same pipeline as tex_material, which gives some sibling differentiation context, though it could be clearer on exactly what distinguishes it from tex_material itself.

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 mentions it's for experiments and visual inspection ('fuer Experimente und Sichtpruefung'), which implies a use case. It also contrasts with 'kein Addon-Schreiben' which implicitly distinguishes it from writing tools. However, it doesn't explicitly state when NOT to use this vs tex_material or tex_emat, leaving the boundary somewhat implied.

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