scene_list

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

With no annotations, the description carries full burden. It does not disclose whether listing is recursive, whether it includes subdirectories, or any side effects. The behavior is implied but lacks details.

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, clear sentence with no unnecessary words. It front-loads the key action and resource. However, it could include more detail without being overly verbose.

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 a simple list tool with one parameter and no output schema, the description is minimally adequate but lacks completeness on recursion, error cases, and file type specificity. It does not compensate for missing annotations or parameter descriptions.

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 only parameter 'projectPath' has no schema description (0% coverage). The description does not clarify the expected format or whether it should be an absolute path, relative path, or project root. The name is suggestive but ambiguous.

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 the tool lists all .tscn files in a Godot project directory, specifying the verb 'lists', the resource 'scenes (.tscn files)', and the scope 'in a Godot project directory'. It naturally distinguishes from sibling tools like script_list.

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 is given on when to use this tool vs alternatives (e.g., scene_nodes), no prerequisites, no context about project structure or path format.

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