Godette

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool retrieves properties but doesn't describe the return format (e.g., JSON, list), potential errors (e.g., invalid paths), or side effects (e.g., read-only, no mutations). This leaves significant gaps for an agent to understand how to interpret results.

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, efficient sentence that front-loads the core purpose ('Get all properties on a specific node in a scene') with zero wasted words. It's appropriately sized for a simple retrieval tool.

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 no annotations and no output schema, the description is incomplete for a tool that retrieves data. It doesn't explain what 'properties' entail or how they're returned, leaving the agent uncertain about the result format. For a read operation with 2 parameters, more context on output behavior is needed.

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 clear descriptions for 'scene' (path to .tscn file) and 'nodePath' (node path within scene). The description adds no additional meaning beyond the schema, such as format examples or constraints, so it meets the baseline for high coverage without compensating further.

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 action ('Get all properties') and target ('on a specific node in a scene'), distinguishing it from siblings like 'modify_node_property' or 'get_scene_tree'. However, it doesn't specify what type of properties (e.g., Godot node properties like position, scripts) or how they're returned, keeping it from a perfect score.

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 provided on when to use this tool versus alternatives like 'get_resource_properties' or 'modify_node_property'. The description implies usage for retrieving node properties but doesn't mention prerequisites, such as needing a valid scene file and node path, or exclusions.

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