list_filesystem

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

Annotations declare readOnlyHint=true, which the description aligns with. The description adds the ADMIN requirement, but it omits the tool's ability to list files via the show_files parameter, which is a behavioral gap beyond annotations.

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 two sentences and immediately front-loads the core action. No unnecessary 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 has a simple profile with an output schema, so return values are covered. However, the description leaves the show_files parameter undocumented in prose and vaguely refers to 'library setup' without detailing the filesystem scope, so there are meaningful gaps for a complete understanding.

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 zero description coverage, and the description doesn't explain the meaning of 'path' or 'show_files'. 'For library setup' only hints at the intended use, not parameter semantics. This is a significant gap.

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 action: 'List server filesystem directories for library setup.' The verb 'List' and resource 'server filesystem directories' make the function unambiguous, and the library setup context distinguishes it from sibling tools like scan_library or list_libraries.

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 phrase 'for library setup' provides a clear use case, and 'Requires ADMIN' sets an access prerequisite. However, it doesn't explicitly mention alternatives or when not to use this tool, so it falls short of full guidance.

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