ue_exec_progress

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

Description explains how to advance the progress bar using enter_progress_frame and mentions a cancel button. This is valuable behavioral context beyond annotations (none provided). However, it doesn't detail error handling or side effects, but the core interaction pattern is well covered.

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?

Concise, well-structured with clear sections for description, usage context, and example. Key information is front-loaded. The example is helpful and keeps it brief.

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?

The tool has a output schema but its structure is not described, and no annotations are provided. The description covers the main usage pattern (progress reporting) and example, but does not explain return value structure or error scenarios. However, for a Python execution tool, this seems sufficient for typical 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?

The parameter descriptions in the example are minimal ('Python snippet to execute', 'Label shown in the Unreal progress dialog', 'Total work units'). Schema coverage is 0%, so description must compensate. It adds some meaning but could be more explicit about the format of code and expected behavior of total_work.

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?

Clearly states it runs a Python snippet with a progress dialog, distinguishing it from exec_python which lacks progress UI. The description explains the purpose and context for long-running operations.

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?

Provides when to use: long-running operations like bulk imports. It doesn't explicitly state when not to use or mention alternatives, but the context is clear enough to differentiate from exec_python.

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