computer_get_screen_size

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

No annotations are provided, so the description must carry the behavioral burden. It does imply a read-only retrieval operation via the verb 'Get' and describes the returned dictionary, but it does not disclose whether 'screen' means primary monitor, current display, or combined desktop, nor any potential error behavior. For a simple getter, this is adequate but not thorough.

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 barely two sentences long fashion, front-loads the core purpose, and includes the essential return information without any filler. Every word earns its place.

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 zero-parameter getter with an output schema, the description is nearly complete. The only meaningful gap is the lack of specification about which screen is being queried in multi-monitor setups, and no mention of when to use alternatives. Still, an agent can confidently invoke it and interpret the result.

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?

The input schema has zero parametersores, so there is nothing for the description to document. Baseline for a 0-parameter tool is 4, and the description appropriately notes the action requires no input without attempting to invent parameter details.

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 uses a specific verb ('Get') and resource ('screen dimensions'), clearly distinguishing this from siblings like computer_get_window_size and computer_get_cursor_position. It even specifies the return shape ('width' and 'height' keys in pixels), leaving no ambiguity about what this tool does.

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 offers no guidance on when to prefer this tool over alternatives. Given siblings like computer_get_window_size and computer_get_desktop_state exist, it would help to explicitly state that this is for the full screen rather than a window or active display, and that no arguments are needed.

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