maximize_current_window

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

The idempotentHint annotation already indicates the operation can be safely repeated. The description adds value by explaining the operation's scope (root window) and the key difference from maximize_window (no elementId required), which helps the agent understand behavior without contradicting annotations.

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 single, focused sentence that immediately communicates the action, scope, and key differentiator. Every word serves a purpose, and the parenthetical clarification is efficient. No wasted text.

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?

Given the tool has no parameters, no output schema, and the idempotentHint annotation covers idempotency, the description is complete. It fully explains what the tool does, its scope, and how it differs from a similar sibling. No gaps remain.

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 0 parameters, so no parameter documentation is needed. The description explicitly clarifies that no elementId is required, which adds meaningful context beyond the empty schema. Baseline is 4 for no params, and the description enhances it.

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 tool maximizes the current session's root window, uses a specific verb ('maximize'), and distinguishes itself from the sibling maximize_window by explicitly noting it operates on the whole window without needing an elementId. This resolves ambiguity in a crowded sibling group.

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 implies when to use this tool (for whole-window maximize without an elementId) and contrasts it with maximize_window, which requires an elementId. However, it does not explicitly state when NOT to use it or mention alternatives beyond the one sibling. The context about elementId provides clear usage differentiation.

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