form_next_element

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

With no annotations provided, the description carries the full burden, and it does disclose the key behavior: focus moves to the next element and the current element is returned. This reveals both the state change and the return value, which is enough for a simple navigation tool, though it does not mention boundary conditions such as reaching the last element.

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 sentence conveys the action and the return value with no wasted words. The verb is front-loaded and the sentence is appropriately sized for the simplicity of the tool.

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 one-parameter navigation tool, the description covers the essential behavior and return value. However, it omits the session parameter's role and does not relate this tool to sibling navigation tools such as current_element or form_previous_element, leaving some contextual gaps.

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 only parameter is session_id, and the schema provides no description coverage (0%). The description does not explain what session_id refers to, why it is needed, or how the default behaves, leaving the agent to infer the parameter semantics from context.

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 states a specific verb ('move focus'), a specific resource ('next form element'), and a return value ('return the current element'). The word 'next' implicitly distinguishes it from the sibling form_previous_element, so an agent can tell them apart without opening schemas.

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 intended use is implied by the phrase 'move focus to the next form element' — it is for forward navigation through a form. However, it does not explicitly mention alternatives like current_element or form_previous_element, nor does it say when not to use this tool.

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