neurover_api_read

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

The description confirms the operational scope (GET request to a route). While annotations already provide safety details (readOnlyHint: true), the description adds the necessary context that this is a generalized web-reading operation, though it lacks specific behavioral details like expected latency or failure modes.

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 definition is extremely concise. It uses only two short sentences to define its function and its selection criteria, ensuring zero wasted language.

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?

Despite the high-level purpose, the tool is complex with five parameters (account, route, page, query, params). Since the description provides no guidance on how to construct valid inputs for these complex parameters, it is contextually incomplete for a robust agent.

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 description fails to add semantic meaning to the complex input parameters (route, query, params). With 0% schema description coverage, the tool does not clarify the functional difference between these inputs (e.g., should 'params' be used for path variables vs. 'query' for URL parameters).

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 provides a clear purpose: reading any website GET route. Furthermore, it explicitly distinguishes itself from the numerous sibling tools by stating it should only be used when no separate specific tool exists.

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 guideline is highly effective. It instructs the agent on when *not* to use the tool (when a specific tool is available), which is extremely helpful for an agent navigating a large API catalogue like the one provided.

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