godot_apply_theme_override

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

The description adds little beyond the annotations. While annotations indicate this is not read-only (readOnlyHint=false) and not destructive by default, the description does not clarify the side effects (e.g., whether the override is permanent, how it affects the scene tree, or if it triggers a re-render). The word 'apply' implies modification, but no additional behavioral detail is provided.

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 a single, concise sentence that directly states the purpose without redundancy. It is well-structured and immediately understandable, with no unnecessary words.

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?

While the description is clear enough for a simple operation, it does not mention return values or persistence (e.g., whether the override saves with the scene). Since the schema covers parameters and annotations cover basic safety, the description is complete for basic invocation but lacks context for edge cases or expected outcomes beyond the operation itself.

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 input schema provides detailed descriptions for all four parameters (node_path, override_type, item_name, value), including type expectations based on the override type. The overall description does not add extra semantic meaning beyond what the schema already covers, so it receives the baseline score of 3 for high schema coverage.

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 action ('Apply theme override'), the target ('Control node'), and the context ('active scene'). It distinguishes this tool from broader theme operations like godot_create_theme by specifying a direct per-node override, though it does not enumerate the override types (which are covered in the schema).

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 provides no guidance on when to use this tool vs. alternative approaches (e.g., creating a theme resource, setting a global theme, or using the LSP for node property changes). It does not mention prerequisites or more suitable contexts, so an agent would have to infer usage from the name alone.

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