godot_advanced_tool

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

The description explains it is a proxy that forwards calls to target tools, which is transparent about its role. However, it does not disclose what the target tools do (e.g., side effects, return values), and annotations provide no safety hints (all false). This leaves room for more behavioral context, but the proxy nature inherently shifts responsibility to the target tools.

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 brief and front-loaded: it states the purpose first, then gives the call format and a list of proxyable tools. Every sentence earns its place with no unnecessary filler or repetition.

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 it is a simple proxy tool with two parameters and no output schema, the description provides sufficient context: the call pattern and the list of available target tools. It could mention that the response mirrors the target tool's output, but this is not critical for a proxy and the overall guidance is adequate.

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?

The schema includes descriptions for both parameters (tool_name and arguments) in Chinese, achieving 100% coverage. The description adds a concrete call format template ({ tool_name: ..., arguments: {...} }), which clarifies how the parameters relate, adding value beyond the schema alone.

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 clearly states the tool is a proxy for calling advanced/deactivated Godot tools, with a specific call format. It distinguishes itself from sibling tools by listing the exact proxyable tool names, making its purpose and scope unambiguous.

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 description explicitly shows how to invoke the tool with an example and lists currently available proxyable tools, giving clear context on when to use it. It does not explicitly state when not to use it, but the list effectively defines its intended usage scenarios.

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