godot_runtime_property

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

With no annotations, the description carries the full behavioral burden. It does disclose the operation is read-only against a bridge, but says nothing about failure modes (node not found, property missing), whether the bridge must be attached/paused, or how values are serialized on return.

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 front-loaded sentence with no wasted words. Brevity is appropriate, though one extra clause on node addressing would have been worth the space.

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?

Two required parameters, no output schema, and no annotations mean the description needs to explain input addressing and return shape. It explains neither, leaving the agent to guess how to target a node and what it gets back.

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 and does not. It never clarifies whether 'node' is a scene path, a runtime pointer, or an instance id, nor whether 'property' is a simple name or a nested property path.

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?

States a specific verb and resource: reading a single runtime Node property via the read-only bridge. The scope word 'one' usefully signals this is a single-value fetch rather than a snapshot (godot_runtime_snapshot exists). It does not explicitly name a sibling it is not, so it stops short of 5.

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 statement of when to use this versus godot_runtime_snapshot, godot_scene_inspect, or godot_runtime_logs, and no prerequisites (e.g. whether the game must be running or paused). The only implied guidance is 'read-only', which the agent must infer the boundaries of.

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