e2e_raw_request

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

With no annotations, the description carries the full burden and does add real value: it discloses automatic API-key/Bearer authentication, project scoping, and error normalization. However, it omits the risk profile of an arbitrary-method tool — DELETE/PUT/PATCH are permitted and nothing warns about destructive or irreversible requests, rate limits, or side effects.

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 sentences, front-loaded with the capability, then the handled concerns, then the doc reference. No filler and no repetition of schema content.

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 raw HTTP escape hatch with no output schema and no annotations, it covers the essentials: scope of endpoints, the two services, auto-auth, scoping, and error handling, plus docs for paths. It falls short only in not steering the agent toward the typed siblings or flagging destructive methods.

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 seven parameters with examples and enums, making the baseline 3. The description only adds the pointer to external docs for valid path structures, which is marginally useful but not parameter-level detail beyond the schema.

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 (execute) and resource (authenticated HTTP request against any E2E Networks REST endpoint) and explicitly frames itself as the generic raw-access counterpart to the typed siblings like e2e_list_nodes and e2e_create_database. An agent can immediately tell this is the low-level escape hatch.

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?

It points to the two API doc URLs for path structures and names the two target services, which implies usage, but it never says when to prefer this over the typed sibling tools (e.g., use e2e_list_nodes rather than a raw GET) or when raw requests are inappropriate. No when-not guidance or exclusions are given for a tool that can hit any endpoint.

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