Godot MCP Bridge

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions '(Compatibility tool)' which hints at legacy or specific renderer context, but provides no details on what statistics are returned, potential side effects, authentication requirements, or performance characteristics. The agent cannot determine if this is a safe read operation or what data structure to expect.

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 brief (7 words), which technically avoids verbosity, but the '(Compatibility tool)' fragment wastes limited space without providing actionable context. It is front-loaded with the action, but the extreme brevity results in under-specification rather than efficient communication.

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 zero schema descriptions, no annotations, and no output schema, the description should explain the tool's behavior, return values, and parameter purposes. It provides none of this. The 'Compatibility tool' label raises questions about deprecation or specific renderer requirements that are left unanswered, leaving the agent unprepared to use the tool 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% for both parameters (timeoutMs and autoConnect), yet the description fails to compensate by explaining what these parameters do. The parameters appear to be transport-level settings rather than domain-specific filters for statistics, which is confusing and unexplained. The description adds zero semantic value beyond the schema names.

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 ('Get') and resource ('project statistics'), but 'statistics' remains ambiguous (performance metrics? asset counts? code analysis?). It fails to distinguish this tool from siblings like get_project_info, get_performance_monitors, or analyze_scene_complexity. The parenthetical '(Compatibility tool)' is jargon without explanation.

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 guidance is provided on when to use this tool versus the numerous sibling retrieval tools (get_project_info, get_performance_monitors, etc.). The cryptic '(Compatibility tool)' label suggests a specific context but offers no explanation of when this compatibility is needed or preferred.

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