toggle_floating

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

With no annotations, the description carries the burden of disclosing behavior. It explains the action enum but does not say what happens when target is null, whether the change affects the focused window or a specified target, or whether the operation has side effects such as toggling layout.

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 short and front-loaded with the core operation, and the action values are listed compactly. It is concise without fluff, though it achieves brevity at the cost of leaving target semantics unexplained.

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 state-changing tool with no annotations and undocumented parameters, this description is incomplete. An agent cannot confidently invoke it because critical context about target resolution and the effect of each action is missing, even though an output schema exists.

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%, so the description must compensate. It adds meaning for the action parameter by listing 'set'|'unset'|'toggle', but it gives no semantics for the target parameter, which remains ambiguous between a window id, workspace name, or null meaning the focused window.

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 a specific operation, 'Set floating state', and tells the agent the possible values for the action parameter. It is clear enough on what the tool does, though it doesn't explicitly distinguish itself from the sibling toggle_special beyond the word 'floating'.

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?

There is no guidance on when to use this tool versus alternatives like toggle_special, focus_window, or switch_workspace. The description implies the purpose but never states a condition or context that would route an agent to this tool.

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