Eden Screen Size

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

The annotation readOnlyHint: true already communicates the read-only nature. The description adds that the value is 'current' and refers to the render coordinate space, but doesn't disclose additional behavioral traits beyond what annotations provide. No contradiction exists.

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 two sentences, front-loaded with the primary action, and every word adds value. It efficiently states what the tool does and when to use it without unnecessary detail.

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, has an output schema, and the description covers purpose and usage. The only missing element is the session_id parameter semantics, which is a minor gap given its optionality and default null.

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 schema description coverage is 0% and the tool description does not explain the session_id parameter at all. With only one optional parameter, the gap is moderate but still leaves the agent guessing about whether and how to provide a session_id.

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's function: 'Get the current Eden render coordinate space in pixels.' This distinguishes it from siblings like eden_get_capabilities or eden_get_runtime_metrics by focusing specifically on screen dimensions, and the mention of touch coordinates reinforces its purpose.

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 gives explicit guidance on when to use these dimensions: 'Use these dimensions for touch coordinates when no screenshot has just been taken.' This provides a clear context and a conditional exclusion, though it doesn't name an alternative tool explicitly.

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