list_filesystem

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

Annotations already establish that the tool is read-only, idempotent, and non-destructive. The description adds the HTTP GET method and indicates that the arguments are query parameters, which is mildly useful operational context, but it does not describe behaviors like path resolution or trailing-slash handling.

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 short and clearly structured with an endpoint and an Args block, so it is not bloated. However, most of the content is redundant with the tool name and input schema, so it earns little credit beyond being compact.

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?

Although the output schema covers return values and annotations cover safety, the description omits crucial context about parameter meanings and does not clarify how this tool differs from sibling filesystem tools. An agent cannot confidently decide what values to pass or when this is the right tool.

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 0%, so the description needed to explain what 'path', 'include_files', and 'allow_folders_without_trailing_slashes' actually mean. It merely restates their names and says they are query parameters, adding no real semantic value beyond the schema itself.

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 says 'Read FileSystem' and gives the endpoint, so it identifies a verb and resource, but it never states what is actually returned (e.g., folders/files at a path). This is vague compared to the closely related sibling tools list_filesystem_mediafiles and list_filesystem_type, and the description does not differentiate from them.

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?

There is no guidance about when to use this tool instead of alternatives. No explicit or implicit preference is expressed, and the large sibling list includes very similar filesystem-related tools, so an agent has no basis for choosing this one.

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