list_scenes

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 merely restates the core function (listing .tscn files) without revealing any additional traits: return format, path semantics, recursion behavior, or handling of invalid paths. This is a thin description that adds little beyond the tool name.

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 that directly states the tool's purpose. No filler or redundant information, and it's front-loaded.

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 has no output schema and no annotations, so the description should explain return values and behavior. It only says 'list all .tscn scene files' without indicating whether it returns relative/absolute paths, whether it defaults to recursive, or how it handles edge cases. Given the simplicity of a list tool, more context is expected.

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 100%, with both 'path' and 'recursive' parameters having descriptions. The description itself adds no extra parameter semantics, but the schema already documents them sufficiently, so the baseline score of 3 is appropriate.

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 'List all .tscn scene files' clearly states a specific action (list) and resource (scene files with .tscn extension). It distinguishes from sibling tools like list_audio_files and list_scripts by specifying the file type.

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 guidance is provided. The description does not mention when to use this tool over alternatives like list_project_files or list_resources, nor does it mention any prerequisites or exclusions. The presence of many similar list_* sibling tools makes this lack of differentiation problematic.

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