get_node_signals

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

Describes return structure in detail, mentions error condition ('Errors if node not found'), and explains the Godot absolute path format issue. Annotations already indicate readOnlyHint=true, and description confirms read-only behavior without contradiction.

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?

Three well-organized sentences: purpose, usage guidance, and return details with path warning. No extraneous words.

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?

All necessary information is present: purpose, usage context, return format, error condition, and path conversion advice. The output schema is absent but the description compensates with a detailed return structure.

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 covers all 3 parameters with descriptions, so baseline is 3. The description adds value by giving an example node path format and explaining conversion, which aids understanding of the nodePath parameter.

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 states 'List all signals defined on a node and their current connections,' which clearly specifies the action and resource. It distinguishes itself from siblings like connect_signal/disconnect_signal by being a read-only listing operation.

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?

Explicitly says 'Use before connect_signal/disconnect_signal to verify signal/method names,' providing concrete when-to-use guidance. Also gives a path format conversion instruction, clarifying a potential pitfall.

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