neuron_research_profiles

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

With no annotations provided, the description carries the disclosure burden, and it does well: it reveals that tabs are opened, scrolling happens to load lazy content, structured extraction occurs, and results are returned in one response. It does not specify the exact output shape or all browser side effects, but the operational behavior is clearly disclosed.

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?

Three tightly packed sentences: what it does, its key constraint and benefit, and when to use it. Every sentence earns its place, and the most important functional detail is front-loaded.

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 operation, the batching model, the URL limit, lazy-load handling, and common use cases. Because there is no output schema, a slightly more specific statement about the shape of the returned structured data would make it fully complete.

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%, so the schema already documents all parameters. The description adds only the 8-URL cap, which is also present in the schema, so it provides no meaningful semantic lift beyond what structured data already offers.

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 names a specific verb ('research'), a specific resource ('multiple URLs'), and a distinctive mode ('in parallel'). It clearly differentiates from the single-page sibling tools by emphasizing batch processing, opening separate tabs, and returning combined results.

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 explicitly states when to use it: batch profile research, multi-page data collection, and side-by-side page comparison. It also implies the alternative of researching one at a time by claiming 5-10x speedup, though it does not explicitly name a sibling tool or list exclusions.

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