set_overlay_offset

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

No annotations are provided, so the description carries the full behavioral burden. It does not say what units the offset uses, whether negative values are allowed, whether the change persists across sessions, or what happens if the overlay is disabled—all material for a mutating setter.

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?

One compact sentence with the important precondition attached rather than buried. Nothing is wasted, though the brevity is partly the cause of the semantic gaps elsewhere.

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 mutation tool with no annotations, no output schema, and an undocumented required parameter, the description is too thin. Units, valid range, and interaction with overlay visibility are all missing details the agent needs to invoke it correctly.

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 0%: the single required 'offset' integer has no description, type range, or units. The description only restates it as a 'floating-offset', adding no meaning such as pixels, direction convention, or valid bounds, so the agent cannot choose a value confidently.

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 (adjusts) and resource (Portal floating-offset), and adds the precondition that it only matters when the overlay is enabled. No sibling tool overlaps with this function, so differentiation is not the issue; it stops short of five only because 'offset' itself is never explained.

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 parenthetical gives a real condition ('only meaningful when the overlay is enabled'), which implies the agent should verify overlay state first. It never points at the obvious companion tool (is_overlay_visible) or states when not to call it, so usage is implied rather than spelled out.

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