manage_texture

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

Annotations provide no useful behavioral signals (readOnlyHint=false, destructiveHint=false, idempotentHint=false). The description mentions mutating actions like 'create', 'bake', and 'set' but does not disclose potential side effects such as overwriting assets, required permissions, or whether operations are reversible. It does not contradict the annotations, but it also adds no behavioral context beyond a generic action summary.

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, front-loaded sentence that succinctly captures the main categories. It is concise and free of fluff. However, given the tool's complexity, the brevity verges on under-specification, though it still earns credit for efficient structure.

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?

This is a highly complex tool (79 parameters, 21 actions, no output schema). The description barely scratches the surface, providing no information about action-specific parameter requirements, return values, or usage patterns. The tool's mechanics (e.g., that a required 'action' dispatches to different operations) are not even hinted at in the description, making it inadequate for reliable agent use.

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 input schema already documents all 79 parameters. The description adds a high-level category summary but does not clarify how parameters relate to specific actions or which parameters are relevant for which sub-operation. Since the schema carries the full parameter burden, the baseline of 3 is appropriate.

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 tool's main capabilities with specific verbs: 'Create procedural textures, process images, bake normal/AO maps, and set compression settings.' This distinguishes it from sibling tools like manage_material_authoring or manage_asset. However, it omits some significant functionality exposed by the action enum (e.g., channel packing, texture groups, streaming), making it slightly incomplete for the full scope.

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 gives no guidance on when to use this tool versus alternatives, nor does it explain that the 'action' parameter determines which sub-operation to invoke. For a tool with 21 distinct actions and 79 parameters, the lack of usage context (e.g., 'use create_noise_texture for procedural generation') is a serious gap.

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