Godot Project 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 doesn't state whether this is a read-only operation, whether it triggers a filesystem rescan, how long it takes, whether it has side effects on the project index, or what the return shape looks like. For a tool with no annotation coverage, 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 no filler words. However, the brevity borders on under-specification rather than genuine conciseness, since it omits critical details about the tool's behavior and parameters.

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?

For a tool with 0% schema coverage, no annotations, and no output schema, the description should be substantially more informative. The scan result type, the maxEntries semantics, and the relationship to sibling scan/search tools are all absent. This is inadequate for an agent to invoke the tool with appropriate parameters and interpret its output.

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 for explaining the maxEntries parameter, but it provides zero information about what maxEntries controls or caps. With 1 optional parameter undocumented in both schema and description, the agent has no way to know whether to set this value or what units/meaning it carries.

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 'Scan the project for scenes, scripts and resources' which names a verb (scan) and resource types, but is vague about what 'scan' produces or what its scope is. Among siblings, there are many other scan-like tools (godot_scene_list, godot_script_list, godot_project_search, godot_editor_filesystem_scan) that could overlap with this function, and the description doesn't differentiate its result from those.

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?

There is no guidance on when to use this tool versus alternatives like godot_project_search, godot_scene_list, godot_script_list, or godot_editor_filesystem_scan. The description provides no context about whether this is a static scan vs a filesystem rescan, nor what differentiates it from sibling tools.

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