toggle_fullscreen

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

Annotations already declare mutating (readOnlyHint=false) but non-destructive and local-scope behavior, so the description's main added value is naming the target as the focused window. It does not say what happens when no window is focused, whether the toggle is reversible, or that it only applies in a Wayland/Hyprland session.

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?

A single front-loaded sentence with zero filler, which is appropriate for a one-action tool. It is borderline terse, leaving no room for the usage or state caveats that would make it more actionable.

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 one-optional-parameter toggle with annotations present and no output schema, the definition covers the essentials and the schema covers the rest. Only the edge case of no focused window and the interaction with sibling window tools remain unaddressed.

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 100% and the mode enum is fully documented in the schema (0=real, 1=maximize, 2=no gaps). The description adds nothing about mode, which is acceptable given the schema does the work, but no extra value is contributed.

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?

States a specific verb (toggle) and a specific resource/target (fullscreen on the focused window), so an agent knows exactly what effect to expect. It does not name or differentiate from related siblings like toggle_float, resize_window, or projector_fullscreen, which keeps it short of a 5.

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 explicit when-to-use or when-not-to-use guidance and no pointer to alternatives such as toggle_float or projector_fullscreen. The only implicit condition is that a window must be focused, which the agent must infer from the phrasing.

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