texture_apply

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

Annotations already establish that this is a non-read-only, non-idempotent, non-destructive, closed-world mutation. The description adds only the face-selection behavior; it says nothing about expected_revision conflicts, texture_ref validity, request_id semantics, whether application is atomic, or what happens on failure.

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 single sentence is front-loaded and free of filler, and the face options are compactly expressed. Its brevity becomes under-specification for a six-parameter mutation, so the structure is efficient but not complete.

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 mutation tool with six required parameters, no output schema, and zero parameter descriptions, the definition provides only face-selection information. Crucial operational context for concurrency tokens, texture references, and selection semantics is missing.

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% across six required parameters. The description clarifies the faces choice and implies that selection must be aligned, but it leaves texture_ref, map_epoch, expected_revision, request_id, and the nested selection fields entirely unexplained beyond their types.

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 identifies a 'Set' operation over orientations or all six faces of a selection, so the basic action is inferable. However, it never states that this applies a texture, nor does it explicitly distinguish the operation from siblings such as geometry_face_set or material_apply.

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?

There is no explicit guidance on when to use texture_apply versus material_apply, geometry_face_set, or texture_catalog. The phrase 'aligned selection' hints at a precondition but does not explain when this tool is the correct choice.

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