sleeper_submit

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

No annotations are provided, so the description carries the full burden. 'Submit form' implies a mutating action but does not disclose side effects, navigation behavior, required browser context, or what happens on success or failure.

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 only two words and front-loaded, but it is under-specified rather than concise. It does not earn its brevity by providing sufficient information for invocation.

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 three-parameter browser automation tool with no annotations and no output schema, the description is completely inadequate. It leaves the agent without enough context to know what a selector or tab refers to or how to invoke the tool 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?

There are three parameters and only the profile parameter has schema documentation, leaving tab and selector undocumented. The description adds no meaning for any parameter, so it fails to compensate for the low schema description coverage.

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 bare verb-resource pair ('Submit form'), but it does not distinguish this tool from closely related siblings such as sleeper_fill_form, sleeper_forms, or sleeper_click. It is more specific than a pure tautology but still too vague to route an agent confidently.

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 when-to-use guidance, no prerequisites, and no named alternatives. The description gives no context for choosing this over the many other form-related tools in the sibling list.

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