Show exported files directory tree

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

No annotations are provided, so the description carries the full burden. It discloses that it lists files with sizes from export/save outputs, implying a read-only inspection. It doesn't mention side effects, but for a listing operation this is adequate.

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?

Two concise sentences, each providing value: the first states what it lists, the second gives usage timing. No redundancy or filler.

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 simple list tool with 3 optional params and no output schema, the description provides purpose and usage context. It doesn't deeply describe return format, but mentions 'with sizes' as a hint. Schema covers parameters, making it sufficiently complete.

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 100% coverage of parameter descriptions, so the baseline is 3. The description doesn't add parameter-specific details beyond the schema, but it indirectly hints at output characteristics (sizes) that relate to maxEntries/depth.

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 folder structure and files from umodel_export/umodel_save with sizes, using a specific verb and resource. It distinguishes itself from sibling list tools by tying to export/save outputs.

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?

Explicitly provides when-to-use context: 'Use this after an export to see what was unpacked.' It doesn't mention alternatives or when-not-to-use, but the context is clear against siblings like umodel_list_objects.

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