midjourney_click

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

With no annotations, the description carries the full burden, yet it never says what clicking actually does — whether it submits a generation, navigates, spends credits, or is irreversible. It also omits failure behavior for invalid element numbers and any indication of what is returned.

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 front-loaded sentence with no filler or repetition. It is efficient, though its brevity contributes to the missing behavioral context rather than reflecting deliberate restraint.

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 mutating browser-automation action with zero annotation coverage and no output schema, the definition leaves out essential context: required session state, side effects, and error handling. The one parameter is fully covered by the schema, but the description does not compensate for the missing behavioral information.

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?

Only one parameter exists and the schema documents it at 100% coverage, including that it is the "Element number from the last read," so the baseline is 3. The description's phrase "numbered element" is consistent with the schema but adds no new meaning such as valid ranges or how numbering is derived.

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 gives a concrete verb and resource ("click a numbered element") scoped to "the current Midjourney page," which is clearly distinct from siblings like midjourney_type or midjourney_read. It stops short of naming or contrasting any alternative, so it is clear but not fully differentiated.

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?

There is no explicit guidance on when to click versus type, read, or close, and no stated prerequisite such as needing an open page or a prior read. The only hints ("current page," "numbered element") are implicit and left for the agent to infer.

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