theme_manage

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 explains important behaviors such as cascading down a Control subtree, clearing when empty theme_path is given, and the acceptance of a session_id. It also notes a compatibility alias for flat parameters, providing context beyond the raw schema. However, it does not mention error handling or side effects of operations like overwriting existing files, though the 'overwrite' parameter mitigates this.

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 efficiently structured with a brief introduction followed by a bulleted list of operations. It is dense with information but well-organized, making it easy for an agent to quickly parse the different op shapes. Every sentence adds value, and the canonical call shape at the end clarifies the expected format without unnecessary 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?

For a complex multi-operation tool with no annotations, the description is remarkably complete. It covers all operations, their parameters, behavior, and the overall wrapping structure. The existence of an output schema means return values are handled separately, so the description does not need to explain them. The description is sufficient for an agent to select and invoke 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?

The description adds substantial meaning to the parameters. While the schema only defines 'op' as an enum, 'params' as a generic object, and 'session_id' as a string, the description details the exact structure of params for each operation (e.g., set_color requires theme_path, class_name, name, and value with color formats). This is critical since the schema has 0% coverage of the nested parameters, and the description fully compensates.

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 that this tool handles 'Theme authoring (Godot's stylesheet-like resource for Controls)' and lists specific operations like create, set_color, apply, etc. This is a specific verb+resource description that distinguishes it from sibling tools like resource_manage or node_manage, which handle other aspects.

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 clear context about when to use this tool (for theme-related operations on Godot Controls) and explains the cascading behavior when assigned via theme_apply. It does not explicitly state when not to use it or name alternative tools, but the specificity of the operations gives enough guidance for an AI to select it for theme management tasks.

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