godot_filesystem

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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions allowed path prefixes ('res:// or absolute') but does not describe side effects (e.g., whether create overwrites, delete is permanent, read returns entire file, search is recursive), error conditions, or permissions.

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 very short (two sentences) and front-loaded with 'File ops' followed by an action list. It wastes no words, but could be considered too terse for the tool's complexity.

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 parameters, no output schema, and a filesystem tool with multiple actions, the description is incomplete. It fails to explain how to structure requests for each action (e.g., required fields in 'params', search patterns, read range) and does not cover return values or error handling.

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 must compensate. It lists valid actions but does not explain the 'params' parameter structure or how to specify paths and additional options. The hint 'path=res:// or absolute' is vague and does not clarify the format of values within 'params'.

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 'File ops' and lists specific actions (list, read, search, create, delete, rename), indicating a file manipulation tool. However, it does not distinguish this tool from sibling tools like godot_editor_read or godot_resource, and the exact scope of 'file ops' is vague.

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 usage guidelines are provided. The description does not specify when to use this tool versus other Godot tools (e.g., for scene manipulation or editor state). There are no when-not or alternatives stated.

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