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

Annotations already cover readOnly/idempotent/non-destructive, but the description adds real behavioral context: the output is an authenticated curl command (auth requirement), it should not be piped into model context, and it gives an engine support matrix (Phaser full, Godot/Unity pending, GameMaker/Unreal artwork-only, Tiled metadata). Only the cryptic 'Recovery artworkOnly must be explicit' clause is left unexplained.

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?

Front-loaded with the core purpose, and every clause carries information, but the style is telegraphic ('Godot/Unity native acceptance is pending', 'Recovery artworkOnly must be explicit') and the dangling final sentence is hard to parse without opening the schema.

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?

There is no output schema, and the description explains what is returned (an authenticated curl command), how to handle it, and the per-engine caveats. It is largely complete, though it does not say whether the command/token expires or how the component-source variant differs in the response.

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 only 33%, so the description must compensate, and it does reasonably: 'whole/selected' maps to packId vs componentIds/sourceComponentId, 'ZIP or component source' maps to the archive vs source extraction paths, artworkOnly gets a usage rule, and engine differences are called out. sourceFormat is still left to the schema.

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 and resource: 'Return an authenticated curl command for a whole/selected UI Pack ZIP or component source.' This clearly scopes it to UI Packs and distinguishes it from get_ui_pack (metadata) and get_export_command (generic). It stops short of naming those siblings explicitly.

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?

'Run locally; never put multi-MB ZIP data into model context' tells the agent how to consume the result, and 'Recovery artworkOnly must be explicit' implies a condition for that flag. However, there is no explicit statement of when to choose this tool over get_ui_pack, get_ui_pack_batch, or get_export_command.

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