neuron_extract_to_json

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

No annotations are provided, so the description should carry behavioral weight. It explains the tool navigates to a URL and returns normalized rows, and mentions pipe-ready outputs. It does not disclose side effects such as navigation changing the current tab, whether the browser context is altered, or rate-limit/pagination behavior. It is not misleading, but it leaves room for more behavioral detail.

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 compact — three sentences covering purpose, behavior, and use cases. The main action is front-loaded, and the use-case clause directly supports agent decision-making. Slight redundancy ('scrape a page and push the data...') means it could be tighter, but it remains efficient.

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 7-parameter tool with nested schema objects and no output schema, the description provides enough context to understand the tool's niche but not complete guidance. It explains the data-pipeline workflow and output flexibility, but doesn't cover pagination behavior, what happens when no selector/schema is provided, auth requirements, or return-value details. The schema carries much of the load, but the description is adequate for basic use.

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 description coverage is 100%, meaning the schema already documents all seven parameters. The description adds the concept of normalized rows and pipeline-ready output but doesn't materially deepen parameter understanding beyond the schema. Baseline 3 is appropriate because the description doesn't contradict or duplicate the schema, but it also doesn't compensate with extra parameter nuance.

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 specifies a concrete verb (extract), resource (structured data from a page), and output format (clean JSON normalized rows), which clearly distinguishes it from siblings like neuron_query_dom, neuron_find_elements, or neuron_evaluate_js. It doesn't explicitly name a sibling, but the data-pipeline focus makes its role clear.

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 states the intended use case: building data pipelines, pushing to a webhook, saving as CSV, appending to a collection. It doesn't give explicit when-not-to-use guidance or name alternatives, but the context is sufficient for an agent to infer when to select this tool over DOM-inspection or JavaScript-evaluation alternatives.

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