ui_manage

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

No annotations are provided, so the description bears the full burden of behavioral disclosure. It merely states 'Godot ui operations' without any details on side effects, permissions, rate limits, or whether operations are destructive. This is insufficient for an AI agent to understand the tool's impact.

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 very short (two sentences) and front-loaded, but the content is minimal. While it is not verbose, it sacrifices completeness for brevity. Every sentence is necessary, but more detail would be beneficial.

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?

This is a dispatcher tool with 9 enum operations and a dynamic params object. Without an output schema, the description should provide more context about what each operation does or how to use params. The lack of behavioral details and parameter semantics makes it incomplete for the complexity.

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 coverage is 100%, with both parameters having descriptions. The tool description adds no additional semantics about the parameters beyond what the schema already provides. The baseline of 3 is appropriate.

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 states 'Godot ui operations' which identifies the resource, but the verb is implicit. It distinguishes from siblings by the UI domain, but does not specify exactly what the tool does beyond that. The instruction to call godot_catalog for the operation tree provides context but the purpose remains vague.

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 gives a hint about workflow: 'Call godot_catalog for the operation tree' implies that this tool is for executing UI operations after looking them up. However, it lacks explicit guidance on when to use this tool versus alternatives, and no exclusion criteria are stated.

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