godot_runtime_snapshot

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

No annotations are provided, so the description carries the full burden. 'Read' plus 'bounded page' weakly signals a read-only, paginated operation, but it says nothing about requiring a running/paused game, cost, whether the snapshot is a point-in-time copy, or failure behavior when no runtime session exists.

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?

One front-loaded sentence with no filler — every clause carries meaning. It is terse to the point of under-specification, but that is penalized under other dimensions rather than for waste.

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?

Four parameters at 0% schema coverage, no annotations, and no output schema means the description is the only guidance available, and one sentence about paging and monitors cannot convey the node-tree shape, depth behavior, or valid monitor identifiers an agent needs to call this correctly.

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% across four parameters. The description only gestures at pagination ('bounded page') and monitor selection ('selected performance monitors'); it never explains limit/offset semantics against max_depth, the allowed monitor names, the depth bound, or the default and maximum values baked into the schema.

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?

Specific verb ('Read') plus resources ('runtime nodes' and 'performance monitors') and a scoping trait ('one bounded page'). This distinguishes it from edit-time siblings like godot_scene_inspect and single-value reads like godot_runtime_property, but it never names those alternatives explicitly.

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?

It implies a runtime-tooling context but gives no when-to-use conditions, no when-not-to-use, and no routing to alternatives (scene_inspect, runtime_property, runtime_logs). An agent must already know the tool landscape to pick this one.

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