godot_assert_node_state

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is conveyed by structured metadata. The description adds the kind of assertions that can be performed, but doesn't mention what happens when an assertion fails or whether the check is synchronous. This is a modest addition beyond the annotations, hence a 3.

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, front-loaded sentence with no fluff or repetition. Every word adds a meaningful assertion category, making it highly efficient.

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 the available annotations, output schema, and schema-provided parameter descriptions, the description is adequate but bare. It names the scope of assertions yet leaves out what 'bounds' means, whether screenshots or waits are involved, and how failure is surfaced. These missing details keep it from being fully complete but still slightly above the minimum viable.

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 reported as 0%, yet the description does not explain the node_path parameter or the structure/keys of the assertions dictionary. The list of 'properties, visibility, disabled state, or bounds' is only a partial sample of possible assertion keys and does not compensate for the missing parameter-level guidance.

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 uses a specific verb ('Assert') and a clear resource (node state), and lists concrete categories: properties, visibility, disabled state, and bounds. This distinguishes it from get/modify/delete siblings at a high level, though it does not explicitly contrast with a sibling by name.

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?

There is no indication of when to use this tool versus alternatives, no exclusionary conditions, and no reference to related tools such as godot_get_node or godot_modify_node. The only cue is the term 'Assert', which leaves usage decisions to the agent.

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