renforge_position_element

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

With no annotations, the description carries the transparency burden. It discloses that the tag keeps its current attributes, explains Ren'Py's integer-vs-float coordinate rule, and implicitly indicates changes are live and not persisted to script by telling users to write final values into the .rpy script.

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 four sentences, front-loading the core purpose and adding only necessary usage details. Every sentence earns its place, with no filler or repetition.

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 has 13 parameters and no annotations, so the description needs to cover a lot. It addresses the core placement workflow and coordinate semantics, but omits details on layer, zoom, rotate, align, and offset parameters, which may be necessary for correct invocation.

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 0%, so the description must compensate. It explains the integer vs float semantics with concrete examples and the requirement of at least one placement field. However, it does not explain the meaning of individual parameters like zoom, rotate, xalign, or offsets, leaving significant gaps for a 13-parameter tool.

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 opens with 'Reposition a shown image tag live and return its new logical bounds,' clearly stating the action (reposition) and target (shown image tag). It differentiates from sibling tools like get_displayable_bounds or click_element by focusing on live repositioning.

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 says 'Provide at least one placement field' and instructs to 'Use this to converge on coordinates interactively, then write the final values into the .rpy script.' This gives clear context for when to use it, though it does not explicitly mention alternatives or when not to use it.

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