imgui_get_window_rect

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

No annotations are provided, so the description carries the burden of behavioral disclosure. The description states it retrieves position and size, which is a read operation, but doesn't disclose the return format, whether coordinates are in screen vs local space, or behavior if the window id doesn't exist. It's a simple read so the transparency is adequate but minimal.

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?

A single, efficient sentence with zero wasted words. Every element contributes to the meaning. No redundancy or filler.

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 read tool with one parameter and no output schema, the description is reasonably complete. It states what is retrieved (position and size). However, it doesn't explain the coordinate system or the unit of measurement, nor how this relates to the window hierarchy. Adequate but could add useful context about returned values.

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%, so the schema already documents the id parameter as 'Window identifier'. The description adds no additional meaning about the id parameter beyond what the schema provides. Baseline 3 is appropriate since the schema does the heavy lifting for the single parameter.

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 (get), resource (window), and the data returned (position and size). It distinguishes from imgui_get_widget_rect (which targets widgets, not windows) and imgui_get_viewport_size (which targets viewport). The purpose is clear though it doesn't explicitly differentiate from siblings.

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 on when to use this tool versus alternatives. It doesn't mention whether it requires a prior window creation, whether the window rect differs from the viewport rect, or note that imgui_get_viewport_size or imgui_get_widget_rect might be appropriate for other cases. Context is implied but no explicit usage direction is given.

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