neuron_fill_and_submit

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

With no annotations, the description carries the behavioral disclosure burden. It explains that it fills fields, optionally screenshots, conditionally submits, and returns a before/after state diff for verification. It could also mention defaults or failure behavior, but the core behavioral contract is clear.

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 concise and front-loaded with the primary purpose, followed by the key behaviors and return value. All sentences earn their place, though the final sentence is more of a rhetorical comparison than strictly necessary.

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 description covers the essential behavior: filling, optional screenshot, optional submit, and the state-diff return value—useful since there is no output schema. It does not address error handling or default timing, but those are secondary for a tool of this complexity.

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 input schema already provides 100% coverage with descriptions for all parameters. The tool description adds context about the overall flow but does not materially deepen understanding of individual parameters beyond what the schema already states.

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 and resource: fill a form and optionally submit it in one call. It also distinguishes itself from the multi-step find → type → screenshot → click workflow, making it easy for an agent to understand what this tool does at a glance.

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 clearly frames when to use this tool—when you need to fill multiple fields and potentially submit in a single operation, replacing the typical manual chain. It also notes that submission is optional, but it does not explicitly name alternatives like neuron_type or neuron_click for simpler single-field cases.

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