List files

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

The annotations already declare readOnlyHint=true and openWorldHint=true, providing the safety profile. The description adds the context of the 'drive host' backend but does not disclose pagination behavior, default limits, response format, or filtering semantics. Since annotations cover the core behavioral safety, a mid-range score is appropriate.

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 sentence that front-loads the primary action ('List files from the Files API'). It is concise and wastes no words, though it could be more informative. The structure is acceptable for such a short description.

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 no output schema and minimal annotations, the description should provide more context about return values, pagination, or differences from sibling tools like kommo_files_entity_list. It does not, leaving the agent with an incomplete picture of the tool's behavior and usage.

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 0%, so the description must compensate, but it merely says 'Supports filters via query params documented by Kommo', which points to external documentation without explaining what filter_name or filter_extensions mean. It adds no value beyond the parameter names already present in 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 clearly states 'List files from the Files API (drive host)', using a specific verb and resource. It distinguishes from siblings like kommo_files_get (which retrieves a single file) and kommo_files_entity_list (which lists files by entity) by focusing on the general files listing operation.

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 no guidance on when to use this tool versus alternatives. It does not mention kommo_files_entity_list or kommo_files_get, and only vaguely notes that filters are supported via query params, without explaining when filtering might be appropriate or how this tool relates to other file-related operations.

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