convert_texture_asset

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

Annotations already signal a mutating (readOnlyHint=false) but non-destructive (destructiveHint=false) operation. The description adds minimal context beyond the word 'new,' implying the source is preserved and a separate asset is produced. It does not address conversion constraints (e.g., alpha-channel handling when targeting JPEG), accepted source formats, or what the tool returns on success.

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?

A single 14-word sentence that front-loads the verb and conveys resource, outcome, and formats. No filler, no redundancy with schema fields, and every word earns its place.

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 two-parameter tool with annotations and a self-documenting enum, the description covers input and outcome. Gaps remain: no return-value information (and no output schema to compensate), no mention of edge cases like JPEG alpha flattening, and no statement of source-format restrictions.

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 coverage is 50% (id described, format not), but the format enum self-documents its values. The description reinforces meaning by mapping 'texture source' to the id parameter and listing AVIF/JPEG/PNG/WebP, which mirrors the format enum—yet it adds no constraints 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?

States a specific verb ('Convert'), resource ('texture source'), and precise outcome ('new AVIF, JPEG, PNG, or WebP texture asset'). The explicit output formats and the 'new asset' framing differentiate it from texture-adjacent siblings such as create_texture_atlas, process_texture_variants, and modify_assets without needing to name them.

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?

No guidance on when to use this tool versus the many texture-related siblings (process_texture_variants, reimport_assets, create_texture_atlas, modify_assets). The intended use case—changing a texture's storage format—must be inferred from the verb and format list; no alternatives, exclusions, or preconditions are given.

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