toggle_fullscreen

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

Without annotations, the description must bear the full burden of behavioral disclosure. It merely says 'Toggle fullscreen' but does not explain the toggling behavior (e.g., from windowed to fullscreen and back), any side effects (e.g., affecting multiple windows), or the existence of the 'mode' parameter. This leaves significant gaps for an AI agent.

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 concise at one sentence with no wasted words. However, it could benefit from slightly more detail without harming conciseness.

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?

The tool is simple but the description lacks critical context: it does not explain what 'Toggle fullscreen' means in terms of state change, nor does it mention the 'mode' parameter or its effect. An agent would need to infer behavior from the schema alone. This is incomplete for a correct invocation.

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% (the 'mode' parameter is fully described in the schema). The description adds no parameter information, so it does not exceed the baseline. No improvement or degradation.

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 'Toggle' and the resource 'fullscreen for the active window', making the tool's purpose understandable. However, it does not differentiate from sibling tools like 'toggle_floating', and it fails to mention that the tool can also maximize, not just fullscreen (as seen in the 'mode' enum).

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?

No guidance is provided on when to use this tool versus alternatives (e.g., toggle_floating, focus_window). The description only implies basic usage without stating prerequisites or exclusions. An agent would have no context to decide between sibling window commands.

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