scene_list

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

Without annotations, the description partially covers behavior by stating the return format ('JSON array containing scene file paths relative to project root'). However, it does not disclose edge cases (e.g., invalid project_path) or whether it is read-only, leaving gaps.

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 concise: a one-sentence summary, category, and structured args/returns. Every sentence adds value with no redundancy or irrelevant detail.

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 existence of an output schema, the description adequately covers purpose, parameters, and return format. For a simple list tool, it provides sufficient context, though error handling and permissions are not addressed.

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?

With 0% schema description coverage, the description adds meaning via an 'Args' section with brief but clear descriptions for all three parameters, including defaults. It goes beyond schema titles but could specify constraints (e.g., directory must be relative).

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 clearly states 'List all scene files (.tscn) in a Godot project' with a specific verb ('List') and resource ('scene files'). Among sibling tools, it distinguishes itself from scene_create, scene_get_tree, etc., as the only listing tool for scenes.

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 description implies usage for listing scenes but does not explicitly state when to use this tool versus alternatives (e.g., scene_get_tree) or provide exclusion criteria. The context is clear but lacks explicit guidance.

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