collect_godot_ui_context

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

No annotations are provided, so the description should fully disclose behavior. It describes a read/collect operation with no mention of side effects, permissions, or what 'bounded static' entails. It does not contradict annotations (none exist).

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?

Two sentences, no wasted words. First sentence states purpose, second references a sibling tool for visual basis. Front-loaded with key intent.

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?

No output schema exists, but description does not hint at return format. Differentiation from sibling tools (e.g., generate_godot_ui_proxy, suggest_godot_scenes) is weak. An agent lacks information to decide when to invoke this tool over others.

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%, yet the description adds no explanation for any of the three parameters (project_path, asset_limit, scene_limit). The agent receives no guidance on parameter values beyond the schema defaults and constraints.

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 it collects Godot UI context (scene, theme, font, etc.) for style support and design. It references a related sibling tool, but 'bounded static' is ambiguous and doesn't strongly distinguish from siblings like generate_godot_ui_proxy.

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 implies using this tool after capture_godot_ui_reference screenshots, but does not explicitly state when to use or not use it, nor provide alternatives. Usage context is only implied.

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