Godot MCP Bridge

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It fails to specify failure modes (exceptions vs return values), blocking behavior (does it wait for the timeout?), or side effects. The 'Compatibility tool' label lacks explanation of what compatibility it ensures.

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 extremely compact at only five words plus a parenthetical. While efficiently worded without redundancy, it errs on the side of under-specification rather than appropriate conciseness, omitting essential usage context that would help an agent construct valid invocations.

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 complexity of additionalProperties: true (suggesting a flexible key-value assertion interface), the description is inadequate. It lacks output schema coverage, provides no example of assertion syntax, and fails to explain how the two documented parameters (timeoutMs, autoConnect) interact with the property assertions.

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 coverage is 0%, requiring the description to compensate. While 'node property value' hints at the purpose, the description fails to explain the critical additionalProperties pattern (where actual property assertions are passed), or clarify the semantics of timeoutMs (wait duration for condition?) and autoConnect (connect to what?).

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 the basic action ('Assert') and target ('node property value'), but remains vague about scope. It fails to explain the tool's unique capability (accepting arbitrary properties via additionalProperties) or distinguish clearly from sibling assert_screen_text, which also performs assertions but on screen content rather than node properties.

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?

The parenthetical '(Compatibility tool)' provides minimal context about the tool's nature but offers no actionable guidance on when to use this versus other assertion tools, nor does it explain prerequisites (e.g., node must exist) or what constitutes a successful assertion.

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