query_nexus

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

With no annotations, the description carries the full behavioral burden, yet it omits auth requirements, rate limits, and the fact that method defaults to GET but can be set to a mutating verb via the free-form method/data parameters. It also says nothing about error behavior for an invalid path. The single useful hint is that the path is caller-supplied and unrestricted.

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?

A single short sentence that is front-loaded and wastes no words, which is structurally good. However, the brevity here reads as under-specification rather than economy, since the sentence cannot support the tool's generic surface area.

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?

An output schema exists, so return values need not be described. But for a three-parameter, untyped gateway passthrough with no annotations and 0% schema coverage, the description is far too thin — an agent has no basis for choosing a path, method, or payload shape.

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 0%, so the description must compensate, but it only alludes to the path parameter ("arbitrary path"). The method and data parameters — including that method is a free-form string defaulting to GET and data is an untyped passthrough object — are left completely unexplained.

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?

States a clear verb ("Query") and resource ("the Nexus gateway"), with the key qualifier that the path is arbitrary, signaling a raw passthrough rather than a typed endpoint. It does not differentiate itself from siblings like query_vibe_proxy or list_nexus_models, which an agent could plausibly confuse it with.

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 statement of when to reach for this generic gateway call versus the more specific sibling tools (list_nexus_models, query_vibe_proxy, detect_nexus). The only implied guidance is the word "arbitrary," which suggests an escape hatch but never says so explicitly or names an alternative.

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