fmod_system_readDir

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

With no annotations, the description should disclose behavioral traits. It mentions a default filter value but does not cover side effects, error handling, permissions, or whether the operation is read-only. The repeated sentence adds no new information.

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 repetitive, with the first sentence appearing twice. A code reference like '[method · system.readDir]' is unhelpful. The text could be shortened to one clear sentence without redundancy.

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?

Given two required parameters, no output schema, and no annotations, the description is incomplete. It does not explain the format of the returned string array, how filters work, or what filePath should be. References to an external enum are insufficient.

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%, and the description adds minimal value. It explains that readDirFiltersFlag is an enum with a default, but does not list enum options or clarify filePath format. It refers to an external enum without providing details.

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 it returns a string array based on filters from a filePath, suggesting a directory read operation. However, it is vague about what exactly is returned and does not clearly differentiate from sibling tools like fmod_system_getFile or fmod_system_getText. Repetition reduces clarity.

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?

No guidance is provided on when to use this tool versus other file-related tools. The description only explains default behavior but does not specify prerequisites, context, or alternatives.

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