Godot Editor Filesystem Scan

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not mention side effects (e.g., whether it refreshes the editor's file tree, whether it can disrupt running scenes, performance implications, or whether it potentially re-imports assets). For a tool that triggers a scan action, this is a significant gap.

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 a single, concise sentence with zero filler. However, it is arguably under-specified rather than appropriately concise — there's room for one or two additional clarifying clauses about behavior or context without bloat.

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 is a no-parameter action with no annotations and no output schema, so the description must carry the full burden. It fails to explain what a 'filesystem scan' entails, what it accomplishes, when it's needed, or any side effects. For a tool that triggers an editor-level operation, this is under-specified.

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 tool has 0 parameters, and schema coverage is 100%, so there are no parameters that need explanation. The 'nothing extra' baseline of 4 applies since there is nothing to clarify semantically.

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 a clear verb+resource ('Trigger a Godot editor filesystem scan'), which identifies the action. However, it does not distinguish itself from siblings like godot_project_scan, godot_file_list, or godot_editor_save_all — a scan is somewhat ambiguous as to what it refreshes or detects.

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 on when to use this tool vs alternatives such as godot_project_scan, godot_file_list, or godot_project_search. It does not explain when a filesystem scan is needed (e.g., after external file changes) or exclusions.

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