get_node_connections

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

With no annotations present, the description carries the full burden of behavioral disclosure. It only states that it 'Gets node signals' without revealing whether it is read-only, what side effects occur, what data is returned, or any error conditions. This is insufficient for an agent to understand the tool's behavior.

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?

While the description is very short, this is under-specification rather than concise effectiveness. It omits essential details, making it unhelpful. A concise description should still be informative within its brevity.

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?

With two required parameters, no output schema, no annotations, and a two-word description, the tool is severely incomplete. An agent cannot reliably invoke this tool without additional knowledge about node signals and connections. The description fails to provide essential context.

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 0%, so the description must compensate. It does not explain the purpose or format of 'scene_path' or 'node_path', nor how they relate to the output. The agent receives no additional meaning beyond the raw parameter names.

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 'Gets node signals' is vague and does not clearly state what the tool accomplishes. The tool name suggests 'node connections' but the description mentions 'signals', which may be a different concept in the Godot engine, creating ambiguity. It fails to distinguish itself from siblings like 'get_node_properties' or 'find_nodes'.

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 for when to use this tool versus alternatives. The description lacks any context about scenarios, prerequisites, or why an agent might prefer this over sibling tools such as 'inspect_scene_tree' or 'get_node_properties'.

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