gmod_zoom

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

No annotations exist, so the description carries the full behavioral burden. It usefully discloses the Windows-only platform constraint and the coordinate interpretation rule, but says nothing about required window state/focus, whether it is a read-only capture, or rate/performance implications.

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 compact sentence block with the critical platform constraint front-loaded in brackets, then the coordinate rule, then the use case. No 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?

No output schema exists, so the description ideally should note the return form, but 'Screenshot + zoom' implies an image result. The main omission is whether the target window must be focused/visible for the capture to succeed, which is material for a screen-capture tool.

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%, so the baseline is 3, but the description adds real meaning the schema omits: that values are percentages of window size, and that values >100 are interpreted as pixels. This disambiguation rule is genuinely useful for correct invocation.

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?

States a specific verb+resource: capture and zoom a region of the Garry's Mod window, with an explicit Windows-only scope. It is clearly distinguishable from gmod_screenshot because it adds a zoom/region capability, though it never explicitly contrasts itself with that sibling.

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?

Gives concrete usage context — 'useful for reading small text, UI elements, console' — which tells the agent when this tool is the right choice. It does not name an alternative or state when-not to use it, so it stops short of full routing guidance.

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