toggle_fullscreen

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

No annotations are provided, so the description carries the full burden. It reveals only that it can set/unset/toggle between fullscreen and maximize, but it does not disclose the target (active window, workspace, monitor), failure conditions, or side effects. The core mutation is clear, but the behavioral context is incomplete.

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 compact two-clause sentence with no filler: purpose first, then the parameter value list. Every segment contributes to selecting values correctly.

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 simple two-parameter tool with an output schema, the essential values are present, and an agent can construct basic calls. However, the lack of usage or behavioral context and the missing target-window semantics leave meaningful gaps for an agent deciding when and how to invoke the tool.

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?

With 0% schema description coverage and no enums in the schema, the description adds critical meaning by enumerating the valid strings for both mode and action. It maps each value directly to its parameter name, making the tool immediately callable. It does not define each value's behavior, though the terms are largely self-explanatory.

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 verb and resource: 'Set fullscreen state.' It adds the applicable mode and action values, and the name plus description distinguish it from sibling toggle_* tools like toggle_floating/toggle_special. It doesn't explicitly differentiate those siblings, but the fullscreen resource makes the intent clear.

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, nor mention of prerequisites such as which window or display is affected. The description only lists mode/action options and leaves the selection context to the agent.

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