generate_godot_ui_proxy

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

No behavioral information is provided beyond the deprecation notice; without annotations, the agent gets no insight into side effects, permissions, or return values.

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?

While short, the description omits essential details, failing to be both concise and informative.

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?

With 8 parameters, no annotations, and no output schema, the description must compensate but provides only a deprecation notice, severely lacking.

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 description adds no explanation of any of the 8 parameters, and schema coverage is only 25%, leaving the agent with insufficient detail to correctly fill parameters.

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 labels the tool as a deprecated alias for capture_godot_ui_reference but does not explain what either tool does, leaving the agent uncertain about its functionality.

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 states 'Deprecated alias', indicating that the tool should not be used and that capture_godot_ui_reference should be used instead, which is clear guidance.

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