preset_fab_list_vault

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

No annotations exist, so the description carries full burden. It discloses that the tool requires external software (`legendary`) and provides fallback instructions. However, it does not explicitly state if the operation is read-only or if it has side effects, though 'list' implies read-only.

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 concise with two sentences, front-loading the purpose and then detailing prerequisites. No wasted words.

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 zero parameters, no output schema, and no annotations, the description adequately explains what the tool does and how to set it up. It could be more detailed about the format of the list or error handling, but it is sufficient for basic 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 input schema has no parameters (0 params), so baseline is 4. The description adds context by explaining the tool's purpose and prerequisites, but since there are no parameters, no further semantics are needed.

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 lists Unreal purchased content from the Epic account (Fab/Marketplace). It specifies the resource ('vault content') and action ('elenca' - list). However, it does not explicitly differentiate this tool from related siblings like preset_fab_download, relying on the user to infer the distinction.

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 setup instructions (requires `legendary` or Epic Games Launcher) but does not explicitly state when to use this tool versus alternatives like preset_fab_download. It implies a prerequisite but lacks explicit 'when-to-use' or 'when-not-to-use' guidance.

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