List Output Files

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 mentions the output format and API endpoint but does not disclose behavioral traits such as whether the operation is read-only, performance implications, or if it requires authentication. The GET method is implied from the endpoint but not explicitly explained.

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 extremely concise: one sentence that includes the purpose, format, and endpoint. It is front-loaded with the core action and efficiently packed without 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?

The tool is simple with one required parameter and no output schema. The description covers the basic purpose and format, but lacks details on how the 'folder##F##file' lines are structured, whether it includes subfolders, or how to handle empty results. However, for a simple listing tool, it is reasonably complete given the schema coverage.

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 description coverage is 100% (the folder parameter is described as 'Folder path (from sdnext_browser_folders)' in the schema). The description adds the output format context but does not add new parameter semantics beyond the schema. Baseline 3 is appropriate.

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 states 'List files in an output folder' with a specific format and API endpoint, clearly indicating the action and resource. It distinguishes from sibling tools like sdnext_browser_folders (lists folders) and sdnext_delete_file (file deletion). However, it does not explicitly contrast with these siblings, so it misses the top score.

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 implies usage by listing files in a folder with a folder path parameter. It does not explicitly state when to use this tool versus alternatives, but the context is clear from the tool name and description. No exclusions or specific scenarios are mentioned.

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