filesystem_manage

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

No annotations are provided, and the description does not disclose behavioral traits such as side effects (e.g., file creation/deletion can be destructive), permissions needed, or any limitations. The agent must infer behavior from operation names, which is risky.

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 (two sentences) but at the cost of clarity. Front-loading 'Godot filesystem operations' is clear but insufficient. The second sentence is a tangential reference, not essential for immediate tool use.

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 the tool supports 10 distinct operations with free-form parameters and no output schema, the description is severely incomplete. It fails to explain operation-specific behavior, parameter requirements, or return values, making it nearly unusable without external documentation.

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 coverage is 100% (both parameters described), but the description adds no extra meaning. The 'params' object is opaque with 'additionalProperties: true' and no guidance on structure per operation. The agent cannot determine required fields for each op without external knowledge.

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 'Godot filesystem operations' which is vague. It does not specify which operations are available (enum does but description lacks detail). The reference to godot_catalog hints at a broader system but doesn't clarify this tool's distinct role.

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 instruction 'Call godot_catalog for the operation tree' implies prerequisite guidance, but there is no mention of when to use filesystem_manage versus other sibling tools like animation_manage or audio_manage. The agent is left without context for selection.

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