scene_nodes

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

The description discloses it parses and returns data, implying a read operation, but lacks explicit statements about side effects, error handling, or performance. No annotations provided, so the description carries full burden.

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?

A single, clear sentence with no wasted words. Could be slightly expanded but remains concise and 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?

Given the simple tool with one parameter and no output schema, the description mentions return content but omits details on error behavior, output format, or usage examples. Adequate but not fully complete.

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 must compensate for the 'scenePath' parameter. It adds no details about path format, validity, or constraints beyond what the schema provides (type and required).

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 it parses .tscn files and returns structure, properties, and resources. This distinguishes it from all sibling tools which focus on other Godot operations.

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?

Implied usage is when you need to parse a .tscn file, but no explicit when-to-use or when-not-to-use guidance is provided. No alternatives mentioned, though no sibling tool appears to do the same.

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