storage_get_files

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

The description adds the 'media files' scope, but does not disclose any additional behavioral traits such as listing order, pagination, or permission requirements. The readOnlyHint annotation already covers safety, so the bar is lower; the description adds little beyond that.

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 a single, concise sentence that immediately states the primary action and resource. There is no wasted wording, and it is appropriately front-loaded.

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?

With a simple one-parameter tool, the schema fully documents the parameter, annotations cover safety, and an output schema exists for return values. The description fully conveys the tool's purpose without needing further elaboration.

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 coverage is 100% for the single parameter folder_path, which is well-described in the schema. The description does not add extra detail about the parameter, so it provides no value beyond 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?

The description uses a specific verb 'List' with a clear resource 'media files in a storage folder'. This clearly distinguishes it from sibling tools like storage_get_subfolders (which lists folders) and storage_get_volumes (which lists volumes).

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 context implies usage for listing media files, but there is no explicit guidance on when to use this versus alternatives like storage_get_subfolders. No exclusions or alternative mentions are provided, leaving the agent to infer based on the name and description.

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