Adapt Image For Cocos

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

With no annotations, the description bears full burden for behavioral disclosure, but it only states the conversion outcome. It omits critical details like required input formats, side effects on original files, permissions, or error behavior. The underlying processing parameters (postprocess) are not hinted at.

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 extremely concise at 12 words. However, for a tool with 4 parameters including a nested object, it may be too brief to be useful. It earns points for brevity but loses some for under-specification.

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?

Given the tool's complexity (4 params, nested postprocess object, no output schema), the description is incomplete. It fails to explain return values, error conditions, or the specifics of the conversion process. A more detailed description is needed.

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 50%, so the description should compensate, but it adds no parameter-specific information. It does not explain how the parameters (e.g., postprocess options) relate to the conversion. The mention of 'transparent PNG' hints at some meaning but is insufficient.

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 converts an existing image into a Cocos-ready transparent PNG, specifying the verb (convert), resource (existing image), and target format. This distinguishes it from sibling generation tools like asset_forge_generate_sprite.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, exclusions, or when not to use it. Users must infer from the tool name alone.

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